the one thing I'd want clarified before rolling multiplayer out to a team is data scope - when a teammate joins my session, do they see just the output, or the actual file paths and browsing history the agent touched along the way? that boundary isn't obvious yet from the launch materials.
DiffSense
The team feature seems like the true hero hero here. No one has done that yet. Anyone know if there is a short version of the 55min video somewhere?
@conduit_design I was thinking the same thing :)
Auto-detecting my existing keys is the part I'd push back on. That key is usually already funding something else, and now a local agent that can run terminal commands is drawing on the same balance with no separate cap. Multiplayer makes it sharper, a teammate's shared session spends my quota and I find out at the end of the month. A per-session token budget in the config would cover most of it.
Dial
the multiplayer piece is what makes me pause a bit. if the agent runs locally and can touch files/browser on my machine, and now a teammate can join my session - do they just see the output, or can they see the actual file paths and browsing history it's operating on along the way? for solo use that's fine, but "shared session" + "local machine access" is a combo I'd want scoped pretty carefully before handing a teammate a live view into my desktop.