Agent threads can be shared like a group order: T3 Code sends guest links, but final approval stays with you

Theo added a beta feature to the T3 Code nightly build: share with guest. The scenario is concrete. Previously, to hand an agent thread to a colleague, you had to copy it, send it out, wait for a reply, screenshot the context, and then feed it back to your own agent. Now you send a link.

This feature was inspired by the group-ordering flow in Uber Eats and DoorDash. After someone gets the link, they can add content to the shared thread, but whether it ultimately runs is confirmed by the initiator. Theo says this flow covers at least half of his thread-sharing use cases, so he built it directly into T3 Connect. The feature is still early; the UI is being left for maria_rcks to finish up. The video was made by Opus 5.5.

The screenshot shows the entry point: 'Share with guest' in the thread menu. Its placement isn't complicated, suggesting the product didn't intend to hide it as an advanced setting.

The replies split into two camps. One camp finds it useful: someone says they needed it a week ago, someone jokes that multi-user sessions have arrived before GTA 6, and an indie developer says they can finally send the link to themselves. The other camp immediately asks about permissions: does the guest get access to the same thread, and can they direct the agent to perform operations on the host's VM? If the guest has the agent delete something and the owner doesn't notice, what happens then? Can the guest access the browser preview and emulator? Theo did not elaborate on these details in the post.

The real difficulty with sharing agent threads is boundaries. With food-delivery group orders, the worst case is ordering the wrong dish; with agent threads, the worst case is changing code, deleting files, or executing commands in someone else's environment. The DoorDash analogy is clever because it separates 'adding content' from 'final confirmation.' But the agent scenario also needs audit logs, permission tiers, revocable links, and a state gap between guest actions and owner confirmation. This time T3 Code only solved the back-and-forth screenshot loop, which is already concrete enough. With the permission questions left unanswered, the beta label is not undeserved. For developers, this feature is worth trying, but don't casually send links to production threads just yet.

Original post: https://x.com/theo/status/2114238361967988747