Skip to content

Codex VS Code extension: rename chats and scope chat list to the current worktree/repository #22853

Closed

Description

@jacobcoro

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.

Activity

  1. jacobcoro commented on May 15, 2026

    @jacobcoro
    Author

    Additional naming request:

    It would also help if Codex could generate better chat titles automatically, with a user-configurable naming rule or template. A few useful patterns:

    • Prefix the title with the current worktree or project name.
    • Use the current plan file or plan name as the base title when sessions are spawned from a plan.
    • Number related sessions consistently when multiple chats come from the same plan or workflow.

    The problem here is less about a pretty title and more about fast retrieval. In practice, I often have several sessions with similar context, and it becomes hard to tell them apart later unless the title encodes the worktree/project and session order.

  2. etraut-openai commented on May 15, 2026

    @etraut-openai
    Contributor

    Thanks for the suggestions. I think these are already requested, so please find and upvote those issues. For future feature requests, please include only one per issue. We generally use upvotes to prioritize feature requests. If you include multiple in a single issue, they do not receive upvotes because it's unclear to the community what they're voting for.

  3. bigweb-ai-agency commented on Jul 24, 2026

    @bigweb-ai-agency

    Hey - icons and colors are cool, but add COMPUTER and PHONE icons to the list !
    no-active-thread-019f9273-a1da-7eb3-be45-89b489e63e78

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestextensionIssues related to the VS Code extension

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions