You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9a58f9b
Browse filesBrowse the repository at this point in the historyBrowse files
feat(server,web,mobile): an agent sets up a link to another environment
A user asks an agent to "delegate this to my vps" without knowing any
address, so t3_environment_link needs none. The agent passes a hint from the
user's words, an environmentId when it knows the machine, or an address only
when the user gave one. The tool records a card in the thread and returns
pending at once, so no provider's tool-call timeout can close it. A machine
already linked here returns linked at once, with no card.
The card lets the user pick the machine from the ones their app knows
(preselected by the hint; "Another address…" for one it does not), and the
access (default supervised, or the agent's suggestion). The client answers
with every address it knows for that machine and a one-use pairing code,
minted there with the user's own session when it can, or pasted. The server
links through the first address that answers as that machine, never sends
the code to one that answers as another, and keeps only the matching
addresses. A machine already linked is answered with "Use this link".
The answer reaches the agent as a notification in its thread: linked (with
the environment id, label and the access chosen), declined, or failed with
the reason. The pairing code is never recorded. Stopping or archiving the
thread closes a pending card; a retry with the same clientRequestId returns
the card's current outcome. t3_environment_unlink undoes a link. Both tools
need a full-access caller and are refused for linked work.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
"List the other T3 Code environments this one is linked to, such as the user's other machines, and whether each answers now. Pass one's environmentId to t3_project_list, t3_thread_launch, t3_thread_list, t3_thread_read, t3_thread_send, t3_thread_wait, t3_thread_interrupt, or orchestrator_capabilities to act there. A linked environment lets this one's agents do at most its access there, and never more than the calling agent may do here. An expired link has to be linked again from a new pairing code.",
282
+
"List the other T3 Code environments this one is linked to, such as the user's other machines, and whether each answers now. A machine the user names that is not listed is not linked yet: call t3_environment_link for it rather than looking elsewhere. Pass one's environmentId to t3_project_list, t3_thread_launch, t3_thread_list, t3_thread_read, t3_thread_send, t3_thread_wait, t3_thread_interrupt, or orchestrator_capabilities to act there. A linked environment lets this one's agents do at most its access there, and never more than the calling agent may do here. An expired link has to be linked again from a new pairing code.",
'Ask the user to link another T3 Code environment, such as their VPS or another machine, so agents here can work there (t3_environment_links). Call it when the user asks to link, connect, or delegate to another machine. You usually do not know where it answers, so pass no address: pass a hint from their words ("vps") and the card lets the user pick the machine. Pass environmentId when a machine the user mentioned names it; if it is already linked, this returns linked at once. Pass url only when the user gave an address. The card lets the user pick the access agents here get there and approve it; their app signs in there with their own session, or they paste a pairing code from there into the card. It returns pending at once: the user answers in the card whenever they get to it, and the outcome (linked with the environmentId to pass to other tools, declined, or failed with the reason) arrives as a message in this thread. End your turn or keep working; do not poll or call it again to check. Never ask for a pairing code in chat.',
"Forget a linked environment, so agents here stop working there. The session there stays listed in that environment's Connections until it is revoked there.",
0 commit comments