IDE extension: offer "Use session directory" or "Use current directory" when reopening a chat from another cwd

Resolved 💬 2 comments Opened Apr 28, 2026 by gryphon2411 Closed Jul 1, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

IDE Extension

What feature would you like to see?

When reopening an existing chat in the VS Code Codex extension, if the saved session was created from a different working directory than the current workspace, please offer a directory chooser similar to the CLI.

For example, something like:

  • Use session directory
  • Use current directory

In the CLI, this kind of flow is already supported when resuming from another cwd. Bringing the same choice to the IDE extension would make it easier to continue earlier chats when switching between repositories, monorepo subfolders, or reopened workspaces.

Suggested behavior:

  1. If the saved session directory matches the current workspace, reopen normally.
  2. If it differs, show a prompt before reopening the chat.
  3. Make clear which directory will be used for file access and command execution.

This would bring the IDE extension closer to the CLI experience for session resume.

Additional information

Observed in:

  • VS Code 1.117.0
  • Codex IDE extension 26.422.30944
  • Ubuntu 24.04.4 LTS
  • Codex CLI 0.125.0

I looked for an existing issue focused on this exact IDE behavior and did not find one.

I did find related discussions about session resume/history in the IDE, but this request is narrower: when reopening a chat from another cwd, the extension should let the user choose between the saved session directory and the current workspace directory.

Thanks for considering this.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

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

  • #18464
  • #19838

Powered by Codex Action

etraut-openai contributor · 1 month ago

This feature request hasn't received enough upvotes, so it is being closed automatically. If you still feel this feature is needed, please open a new feature request with an updated title and description.