codex - 💡(How to fix) Fix Ability to permanently move an existing thread to a different project/workspace [1 comments, 2 participants]

What variant of Codex are you using?

App, CLI

What feature would you like to see?

A supported way to permanently move an existing thread from one project/workspace to another.

Today, if a thread was originally created under one project, there does not seem to be a way to re-home it so that it permanently belongs to a different project in the Codex app.

Why this matters

A common workflow is:

1. Start work in one folder/project
2. Later create, rename, or reorganize the actual project folder
3. Want to keep the existing thread history, but have that thread live under the new project going forward

Right now, I can find ways to temporarily run a thread against another directory via the CLI/TUI using codex resume, but I cannot find a way to permanently move that thread to a new project in the Codex app.

Suggested solutions

Any of these would solve the problem:

• Add a “Move thread to project…” action in the Codex app
• Add a CLI command to permanently rebind a thread to a new project/workspace
• Support this in resume/fork flows with an explicit persistent move option
• Support project rename/move migration so existing threads follow the new project location

Example use cases

• Renaming a project folder after a thread already exists
• Moving work from a scratch directory into a real project folder
• Reorganizing projects in the app without losing thread history
• Moving a thread between related repos/worktrees while preserving continuity

Additional note

This request is specifically about permanently moving an existing thread to a new project. Temporary runtime directory switching is not sufficient.

Additional information

No response