Feature request: allow moving conversations between projects #24519

Activity

1. github-actions

   added

   enhancementNew feature or requestNew feature or request

   codex-webIssues related to Codex WebIssues related to Codex Web

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   on May 26, 2026
2. github-actions commented on May 26, 2026

   

   github-actionsbot

   on May 26, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • Clarify new-thread context and support moving threads between General and Projects #24222
   • Allow stored Codex threads to be associated with a project cwd after planning #23313

   Powered by Codex Action
3. Lee-take commented on Jun 19, 2026

   

   Lee-take

   on Jun 19, 2026

   More actions

   Adding another workflow where this feature is especially important:

   A project often starts as an ordinary conversation before the user knows it deserves a dedicated Codex Project. That early thread may contain the goals, requirements, architecture, constraints, tradeoffs, implementation plan, and rationale behind major decisions. Once the direction is clear, the user creates or selects a Project. At that point, the original planning conversation should be movable or attachable to that Project, because it becomes part of the project's working history.

   Without this, the project record is fragmented:

   • Planning and architecture stay stranded under general Chats.
   • Implementation continues under the Project.
   • Future Codex runs lose the context behind earlier design choices.
   • The user has to manually summarize context, which is lossy and easy to forget.

   Expected behavior that would cover this workflow:

   • Add Move to Project or Attach to Project from an existing conversation's menu.
   • Add Add existing conversation from inside a Project.
   • Support Chats -> Project, archived conversation -> Project, Project -> Project, and optionally Project -> Chats.
   • Preserve messages, attachments, generated files, tool activity, timestamps, and chronology.
   • Make attached conversations available to project-scoped search and future Codex context retrieval, not only as a visual sidebar item.
   • If a full ownership move is risky, distinguish Move from Attach/copy: moving changes the conversation's project association; attaching keeps the original location but makes the thread part of the target Project's context.

   This is not only about cleaning up a conversation that was accidentally started in the wrong place. It also supports a common real workflow: explore first, decide it is a project later, then promote the planning history into the project.

   Related context: #22345 covered the broader Chats <-> Projects move request, and #20115 covers archiving/exporting conversations as project artifacts.
4. daryll-swer commented on Jun 20, 2026

   

   daryll-swer

   on Jun 20, 2026

   More actions

   Agreed, this is a must-have feature. I often start with a general chat before knowing which project owns the work, then later need to attach it to the right project. Starting a fresh thread and manually summarising context is lossy and fragments the project history.
5. Lee-take commented on Jun 20, 2026

   

   Lee-take

   on Jun 20, 2026 via email

   More actions

   Thanks, Daryll. I completely agree with this. And I also want to say a genuine thank you to the Codex team. Codex has become a very important part of my daily work. It saves me a lot of time, helps me keep context across complicated tasks, and has honestly improved my productivity more than any tool I’ve used before. This particular feature matters a lot to me because it matches a very common workflow: I often start in a general chat before I know which project the work really belongs to. Later, when the work becomes clearer, I want to attach that existing thread to the right project instead of starting over and manually summarizing everything. That manual step always loses some context and makes the project history feel fragmented. If the team doesn’t have time to pick this up soon, I’d be very happy to work on it myself. I’m confident I can implement this feature independently. What I’d need is simply a path to submit a PR, so your team can review it properly. I understand that Codex may not currently accept PRs from regular users, and of course I’d respect whatever process the team needs. But I hope you’ll trust that I would handle this carefully, keep the change focused, follow the existing code style, and leave the final decision entirely to the maintainers. Thanks again for considering this. This would make a real difference in how I use Codex every day. 原始邮件 发件人：Daryll Swer ***@***.***&gt; 发件时间：2026年6月20日 23:27 收件人：openai/codex ***@***.***&gt; 抄送：Lee-take ***@***.***&gt;, Comment ***@***.***&gt; 主题：Re: [openai/codex] Feature request: allow moving conversations between projects (Issue #24519) daryll-swer left a comment (openai/codex#24519) Agreed, this is a must-have feature. I often start with a general chat before knowing which project owns the work, then later need to attach it to the right project. Starting a fresh thread and manually summarising context is lossy and fragments the project history. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS&nbsp;and Android. Download it today! You are receiving this because you commented.
6. Andreuha commented on Jun 23, 2026

   

   Andreuha

   on Jun 23, 2026

   More actions

   How is this not already prioritized?

   👍React with 👍4Reacted by GGBondBlueWhale, Biel Casals, PS and The Beach Lab
7. saidelike commented on Oct 14, 2026

   

   saidelike

   on Oct 14, 2026

   Last edited by saidelike

   More actions

   Oh just saw the label is codex-web. My below comment is for codex Desktop App.

   In some unknown scenario, I've seen this shown and it allowed me to move it to another project (in my case it was another worktree of the same repo, but created as another project)
   

   But I can't move any of the other conversations from on project to another (even the same repo but different worktree) as this option does not show. Not sure why...