/cd for threads: move a thread to another folder and keep going

[N4M3Z]

Claude Code has /cd <path>: the session moves to another folder and the conversation continues. I'd like that in T3.

A thread often starts in one repo, and the work potentially ends up in another. Today the only way out is a new thread and a pasted summary afaics. #26767 moves a thread into a project only when the folder stays the same.

Scope:

• /cd <path> in the composer, where <path> is the root of an existing project. The thread moves to that project, and the next turn runs there.
• Idle threads only. Threads with subagents are refused. Branch and worktree are cleared, as in feat: turn a No project thread into a project #26767.
• The provider session moves with the thread. Claude stores transcripts per folder, so T3 has to carry the session over, as Claude Code's /cd does.

Would you take a PR for this? Related: #23882.

[cveld]

+1, with a case where the destination folder is a new project that did not exist yet, and where the thread was driven by an agent.

I started a thread under No project (scratch folder) to look into something, and it turned into recurring work that belongs in its own project folder. I asked the agent to create that folder, register it as a T3 project, and move the thread there. It could do the first two with t3_project_create, but found no tool to re-home the thread:

• t3_thread_update only renames or regenerates the title, and says "Workspace and branch cannot change here."
• t3_thread_transfer (fork) keeps the same setup, so the fork stays in the same folder.
• t3_thread_launch starts a new thread rather than moving this one.

So the fallback was a new thread in the new project with a hand-written summary of the old one, which is the workaround described above. The old thread's history stays behind in the scratch folder.

Two details that matter for this workflow:

1. The move should be reachable by the agent (MCP/CLI, not only a composer /cd), since in my case the agent was the one asked to do it. #23882 proposes the same for t3_thread_update.
2. Scratch-to-project is the common case. #26767 covers it only when the scratch folder itself becomes the project root; it does not help when the destination is a different, already existing folder, which is the case /cd <path> would cover.

Written with Claude in T3 Code, on behalf of @cveld.

[N4M3Z]

PR is up: #33342. I didn't wait for an answer here, hopefully it doesn't get closed.

It goes a bit further than the scope above. /cd takes any folder, and a folder without a project becomes one. /no moves the thread to a new scratch folder. Subagents and side chats move along. Claude's transcript moves with the session, and earlier turns keep their links and diffs in the folder they ran in.

The scratch-to-new-project case above works from the composer. For a move started by the agent, see #32163.