t_messinis

Multi-agent + MCP in a browser tab is a clean demo surface. The question I'd ask: does the studio represent agent topology as data (so you can serialize / version/diff it) or is it implicit in the UI graph? We found the former matters a lot the moment you want to test the same workflow against two different models, or roll back a change someone made in prod.

Curious about the security model here. Giving an agent access to SMS, contacts, and the ability to send email from my phone is a pretty large capability surface — what's the approval flow look like? Is it per-tool-call, per-session, or do you grant broad scopes up front? The MCP tool-use pattern where everything gets pre-approved feels risky for something like "send email," and I'd be interested to know how you're thinking about the difference between "agent reads my calendar" and "agent sends an email as me.