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 d2871b3
Browse filesBrowse the repository at this point in the historyBrowse files
feat(server): hand a thread off to a linked environment
A thread can now move to a linked environment with its conversation and its
git work, with exactly one copy live. ThreadHandoff marks it departing,
which refuses new turns and keeps queued runs from starting; packs the
branch and working tree with HandoffGit; uploads the bundle through the
other side's signed attachment route; and calls t3_thread_import there,
which now takes the bundle and applies it in a new worktree before creating
the thread. Only then is the thread departed here and read-only. A failed
move marks it failed, which takes turns again, and nothing is left there.
An agent can move its own thread with t3_thread_handoff. The move then
waits as pending until its turn ends, starts the thread there with the
agent's continuationPrompt, and is cancelled by a user message sent before
the turn ends. A startup sweep runs moves that a restart cut short; import
ids derive from the handoff, so a retry finds the thread already there.
threadHandoff.options / start / cancel serve the clients.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
"Move a thread to a linked environment (t3_environment_links), such as the user's VPS, with its conversation and its git work: unpushed commits, uncommitted edits and new files. It continues there in a new worktree of the project with the same repository, and the copy here becomes read-only. Omit threadId to move the calling thread: the move then happens as soon as this turn ends, and continuationPrompt becomes its first message there, so end the turn after saying what you will do there. A message to the thread before then cancels the move. Another thread must be idle to move.",
"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.",
0 commit comments