Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex VS Code extension: rename chats and scope chat list to the current worktree/repository

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

In multi-worktree and monorepo workflows, generated chat titles are not enough to quickly find the right conversation. Being able to rename chats would make saved context easier to manage. Scoping the chat list to the active worktree/repository would reduce confusion and lower the chance of continuing the wrong thread.

RAW_BUFFERClick to expand / collapse

Feature request

Please add two related improvements to the Codex VS Code extension:

  1. Allow users to rename a chat/thread after it is created.
  2. Scope the visible chat list to the current worktree or repository context, so chats from other worktrees/repos do not show up unless the user explicitly switches context.

Why this matters

In multi-worktree and monorepo workflows, generated chat titles are not enough to quickly find the right conversation. Being able to rename chats would make saved context easier to manage. Scoping the chat list to the active worktree/repository would reduce confusion and lower the chance of continuing the wrong thread.

Suggested behavior

  • Provide a rename action in the chat list or thread header.
  • Show the current worktree/repository association for each chat.
  • Default the list to chats from the active worktree/repository only.
  • Optionally offer a broader "all chats" view for users who want it.

If this is already possible behind a flag or setting, exposing it in the UI would still be useful.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#model download#tokenizer error#prompt formatting#chain error#conversation history

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex VS Code extension: rename chats and scope chat list to the current worktree/repository