Feature request: allow rebinding an existing Codex Desktop conversation to a new workspace folder

Resolved 💬 1 comment Opened Apr 18, 2026 by fsrmll Closed Apr 18, 2026

What feature would you like to see?

When a Codex Desktop conversation was started in folder A, and that folder is later moved or renamed to folder B, there should be a user-friendly way to rebind the existing conversation/thread to the new workspace folder.

Right now, the thread still appears tied to the old path. In practice this means the conversation context is still useful, but the workspace association becomes stale, and actions like opening the folder from the thread UI are no longer correct.

Proposed UX

Add a thread-level action such as:

  • Change workspace folder
  • or Relink workspace

A good place would be the thread context menu / overflow menu in the sidebar.

Suggested behavior:

  1. User chooses Change workspace folder on the current conversation.
  2. Codex opens a folder picker.
  3. Codex updates the thread's working directory for subsequent turns.
  4. Codex refreshes related workspace-derived state such as:
  • open-in-file-manager target
  • git metadata shown for the thread
  • trust / sandbox / skills resolution for the new folder

Why this matters

This comes up naturally when users reorganize projects, rename folders, or move work into archive/versioned directories after the conversation has already started.

Without a rebind action, the current workaround is awkward:

  • go to the new folder manually
  • resume the old conversation from there
  • rely on cwd selection behavior outside the desktop UI

That works in some cases, but it is not discoverable from the desktop app itself.

Suggested fallback behavior

If the stored workspace path no longer exists, Codex could also offer a lightweight recovery prompt, for example:

  • Original folder not found. Locate moved folder?

This would make the workflow much more resilient after project renames/moves.

Additional context

This request is specifically about the desktop app UX. The underlying concept of switching/overriding the thread cwd for subsequent turns already seems to exist elsewhere in Codex, but there is currently no obvious, user-friendly desktop action for it.

Related adjacent issues I found while searching:

  • #2252
  • #4791
  • #5876

Those look related to cwd/session behavior, but this request is focused on a desktop-side relink/rebind workflow.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗