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
Move an existing thread to a new worktree from the UI
#15999
Asking the agent to call t3_worktree_handoff is a great way to move a thread into a worktree, but you have to know that it exists. When I started using T3 Code, I couldn't find this option anywhere in the UI, so I assumed T3 Code couldn't do it at all. The Codex app, which I came from, has it in the UI.
It would be great to have a Move to new worktree action on existing threads, so this is discoverable without knowing about the MCP tool.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Asking the agent to call
t3_worktree_handoffis a great way to move a thread into a worktree, but you have to know that it exists. When I started using T3 Code, I couldn't find this option anywhere in the UI, so I assumed T3 Code couldn't do it at all. The Codex app, which I came from, has it in the UI.It would be great to have a Move to new worktree action on existing threads, so this is discoverable without knowing about the MCP tool.
Related: #3753
All reactions