Repository navigation
Closed
Labels
enhancementNew feature or requestNew feature or requestextensionIssues related to the VS Code extensionIssues related to the VS Code extension
Description
What version of the IDE extension are you using?
0.4.76
What subscription do you have?
Chatgpt plus
Which IDE are you using?
VS code
What platform is your computer?
Linux 6.17.9-76061709-generic x86_64 x86_64
What issue are you seeing?
What is the problem?
In the Codex VS Code extension, task/thread titles stay auto-generated and I can’t edit them.
When I switch between many tasks, it becomes hard to find an older one because I can’t rename titles to something meaningful for my workflow.
Current behavior
- Title is auto-generated
- No option to edit/rename the title in the extension task/thread history
- I have to open multiple tasks/tabs to figure out which one is the one I need
Expected behavior
- Add a
Renameaction for tasks/threads in the VS Code extension (context menu and/or inline edit) - Keep auto-generated titles by default, but allow manual override
- Persist custom titles across restarts/sync
- (Optional) add search/filter support that uses renamed titles
Why this matters
Custom naming makes task history much easier to scan and reduces context-switch friction, especially when working on multiple parallel tasks.
Reference UX
ChatGPT web supports editing auto-generated conversation titles. A similar capability in the VS Code extension would solve this issue.
What steps can reproduce the bug?
- Open VS Code with the Codex extension installed.
- Start multiple tasks/chats so the sidebar/history contains several auto-generated titles.
- Try to rename one of those task/chat titles from the Codex sidebar/history (context menu/title area/actions).
- Observe there is no working way to edit the title (it remains auto-generated).
- Try to return to an older task; it is difficult to identify quickly because custom titles are not possible.
What is the expected behavior?
No response
Additional information
Task/chat titles should be editable in the Codex VS Code extension.
Expected:
- A Rename action is available for each task/chat.
- I can replace the auto-generated title with my own title.
- The custom title is saved and shown in history so old tasks are easy to find.
Reacted by Mateen Ulhaq, bhack, denyeo, wangheng86, d-w-d, maskeda, Goma, anddam, Julio Xavier Terez , James Martin and 105 more
Reacted by petruha98, FEmser, Adrien KERFOURN, Kwame Oteng Appiah-Nti, Alexey Vekshin, Jason Hu, TaeeunKil, BF4C5B1330, BruSkills, paularduin and 91 more
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestextensionIssues related to the VS Code extensionIssues related to the VS Code extension
Activity
github-actions commentedon Feb 23, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
nguyenbs commentedon Feb 24, 2026
Pls make this happen
anowardear062-svg commentedon Mar 9, 2026
Thanks
shawnlee-info commentedon Mar 9, 2026
Hey OpenAI, great you tagged this as "enhancement" not "missing essential". At this point I'm not even that expecting this feature, I'm only curious how do you creators use this extension daily on multi tasks? How do you tell which is which from those hilarious auto summarized titles? Or do you even use it daily?
etraut-openai commentedon Mar 9, 2026
@shawnlee-info, most of the internal OpenAI usage of Codex has switched from the IDE extension to the Codex app. We also still have a large fraction of users who prefer the CLI. The app's UI was designed to handle multiple concurrent tasks and provides features like worktree management, PR creation, review mode, thread pinning, and thread renaming. The IDE extension is more limited. Some of those limitations come from the host (VS Code or Cursor) and others come from the smaller screen real estate afforded by the side panel. I personally still use the IDE extension for some tasks where it's useful to select code in an editor, but I'm now doing most of my work in the app.
I think this is a good feature request, and I'd like to see this added at some point. It's just currently prioritized below many other feature requests when measured by upvotes.
shawnlee-info commentedon Mar 9, 2026
thanks, I just noticed the Codex App is now available for Windows a few days ago , that's a great job👏. Please understand our frustration before as the IDE extension is the only official way for developers on Windows.
Hope the extension still gets updated at some point though.
When asking this issue on OpenAI forum recently, "OpenAI Support" used Copilot Chat UI screenshot to answer me yes😅
mahezsh commentedon Mar 9, 2026
I’d be happy to contribute this if extension PRs are open to community contributions. Is there a public repo/path for that @etraut-openai? 🙂
YodaEmbedding commentedon Mar 10, 2026
SantoshSrinivas79 commentedon Mar 10, 2026
Having the same issue, is there any place we can go and change it manually ourselves in the mean time
etraut-openai commentedon Mar 10, 2026
@SantoshSrinivas79, the Codex CLI and Codex app both support thread renaming.
SantoshSrinivas79 commentedon Mar 10, 2026
hi @etraut-openai ... i am using the codex extension in vs code ... is it possible there?
61 remaining items
etraut-openai commentedon May 30, 2026
The latest version of the Codex IDE Extension now supports renaming and archiving!
omry commentedon May 30, 2026
Awesome.
@etraut-openai, can you please reopen the related #17185 to solicit more community feedback?
daxliniere commentedon May 30, 2026
Amazing. Thanks @etraut-openai !!
daxliniere commentedon May 30, 2026
Yes, agree this is a very useful thing. When I'm working on an Arduino project, I don't need to see web development threads.
etraut-openai commentedon May 30, 2026
@omry, #17185 was closed because it didn't receive enough community feedback. If you'd like to see a feature like that, please open a new feature request. Sometimes feature requests fail to get enough upvotes because of the title or description, so it's good to create a new one to try to attract more attention from users.
omry commentedon May 30, 2026
@etraut-openai,
Thanks for responding.
I think #17185 is well articulated, and the title seems reasonable.
I also run a few large repos with large backlogs, so I definitely appreciate the urge to close issues that are not getting enough community signal, or that do not seem aligned with the general direction of the project.
That said, I think there is a decent chance this one was overlooked by the community because people are less likely to search for a second-order solution like project-based chat isolation than for the more obvious one: "let me rename chats".
We are already seeing renewed interest there, likely primarily from people coming from this issue. That suggests the lack of prior activity may not have reflected lack of need, but rather discoverability.
Also, this comment points out that the feature already exists in Codex CLI and is enabled by default:
#17185 (comment)
Assuming that is accurate, it suggests OpenAI already recognizes this as an important part of the workflow.
Instead of creating a new issue, I suggest reopening the existing one with a time box. For example, declare that it will stay open until a specific date, perhaps three months from now. During that window, the community will have a chance to express their opinion. If there still is not significant enough interest after that, you can close it without second thoughts.
rowsof commentedon May 30, 2026
@etraut-openai I think the community has a hierarchy of needs, now that this one is satisfied you'll find significantly more interest in #17185
Do you prefer someone duplicate the request exactly as written, or reopen?
Thanks for the hard work!
omry commentedon May 30, 2026
Per @etraut-openai’s guidance to open a fresh feature request, I opened #25319 for the related VS Code extension request: workspace/project-scoped chat history so threads from unrelated projects are not mixed together.
For people seeing this:
If per-project chat isolation in vscode is important to you, please upvote.
whatsupbros commentedon May 30, 2026
@etraut-openai I see it received quite some community support after it has been closed. And opening a new request would mean losing the history, wouldn't it?
morganross commentedon May 30, 2026
SoymilkWinsAgain commentedon Jun 12, 2026
I’m also running into this heavily in the VS Code Codex extension.
My main problem is not only cosmetic naming. When I fetch / resume many Codex cloud tasks or local conversations, the thread list becomes hard to distinguish, and I often select the wrong conversation. ChatGPT’s main app gives each conversation a useful generated title, but the IDE extension currently does not give me enough control or clarity for high-volume usage.
What would help:
This becomes especially important when several conversations are about similar repos or similar tasks, because first-message snippets or weak generated titles are not enough to safely identify the right thread.
omry commentedon Jun 13, 2026
Codex maintainers indicated that this one was already closed due to lack of community interest and that a new issue should be opened for it.
To anyone else reading this, please do not create additional noise here. allow this message to be the last on this issue.
Direct your support at #25319.
daxliniere commentedon Jun 15, 2026
@SoymilkWinsAgain, try this tool for now: https://github.com/daxliniere/VS-Codex-Thread-Tools-renamer-search
whatsupbros commentedon Jun 15, 2026
@SoymilkWinsAgain, @daxliniere, the feature to rename threads was already implemented some time ago, see #12564 (comment), and you should already be able to rename threads in latest VS Code extension versions.
So this issue ticket is closed.
Please give your support to #25319, which is a natural continuation.