Allow renaming task/thread titles to improve history navigation

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

• #12552

Powered by Codex Action

Pls make this happen

Thanks

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?

@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.

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😅

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? 🙂

Related bug(s):

1. In VS Code, create a task.
2. In Codex App, rename the task.
3. In VS Code, prompt task with "bye world".
4. Restart VS Code and Codex App.

The task name will be reverted back to the old task name.

Having the same issue, is there any place we can go and change it manually ourselves in the mean time

@SantoshSrinivas79, the Codex CLI and Codex app both support thread renaming.

hi @etraut-openai ... i am using the codex extension in vs code ... is it possible there?

@SantoshSrinivas79, that's what this feature request is asking for.

nevermind .. i tried it in codex and i understand what you meant :-D

Hello, thanks for the clarifications.
I'll switch to the Codex app for the time being.

While I appreciate the Codex App for Windows, I never thought one day Github Copilot Chat (VS Code Extension) can hit me again with Codex Extension's defects.

Codex VS Code Extension
👍: Can use my own API key
⛔: 1) CAN NOT rename sessions. 2) DOES NOT separate Sessions between projects (workspaces)

Github Copilot Chat
👍: Almost perfect UI: 1) CAN rename Sessions. 2) DOES separate Sessions between projects (workspaces)
⛔: Limits to 300 requests for gpt-codex models, CAN NOT use my own API key for those models

The Merge
After recent update, Github Copilot Chat now shows all sessions from Codex as well, but keeps the two defects: Can't rename, doesn't separate between projects. Now even my Copilot Chat Sessions list is FLOODED with codex sessions that I can't rename from other projects

It is not an ideal solution, but I thought I would share it. I can rename sessions by editing the ~/.codex/session_index.jsonl file, then running Developer: Restart Extension Host from the Command Palette to refresh it without restarting VS Code.

It is not an ideal solution, but I thought I would share it. I can rename sessions by editing the ~/.codex/session_index.jsonl file, then running Developer: Restart Extension Host from the Command Palette to refresh it without restarting VS Code.

Great workaround ♥, appreciate it. I tried similar hack before but I was misled by a reply to modify the /sessions/year/month/individual-session.jsonl and didn't work.

To let it refresh we can also disable/enable the ext.

It is not an ideal solution, but I thought I would share it. I can rename sessions by editing the ~/.codex/session_index.jsonl file, then running Developer: Restart Extension Host from the Command Palette to refresh it without restarting VS Code.

Thanks for sharing! Wrote an automatic script for this based on your workaround and thought I would share it. As a warning, this hasn't been rigorously tested -- I've only tried it on the most recent extension version (26.311.21342)

python scripts/rename_codex_thread.py \
  --thread_id "$CODEX_THREAD_ID" \
  --name "New Thread Name"

It's not the most elegant strategy, but the way I use it is by pointing codex to this script inside a thread and asking it to rename the current thread. Once it does so, I just reload VSCode (developer reload window) and the name refreshes.

Additional details:

• The tricky part is of course resolving the thread_id, and the strategy for both searching and renaming changes depending on where the session is stored.
• For some reason not all sessions are in ~/.codex/session_index.jsonl and are instead in ~/.codex/state_5.sqlite. This seems to be the case for older threads vs newer ones. The "hacky" workaround I found was that you can just copy the id and date to add a new entry into session_index.jsonl with a new thread_name and rename it that way.
• Searching which thread to rename can be tricky, as those in session_index.jsonl have short names, but those in state_5.sqlite have the full first message under title, so you'd need some kind of fuzzy search to properly resolve the correct thread ID for some threads.
• Inside the current thread sandbox however, there's an environment variable called CODEX_THREAD_ID that shows this directly, which is why you can just "ask the agent" to change it's "own" thread name. Of course, to save on usage you can always just ask codex once to return CODEX_THREAD_ID and then run the script manually yourself every other time afterwards.

Thanks for sharing! Wrote an automatic script for this based on your workaround and thought I would share it. As a warning, this hasn't been rigorously tested -- I've only tried it on the most recent extension version (26.311.21342) python scripts/rename_codex_thread.py \ --thread_id "$CODEX_THREAD_ID" \ --name "New Thread Name" It's not the most elegant strategy, but the way I use it is by pointing codex to this script inside a thread and asking it to rename the current thread. Once it does so, I just reload VSCode (developer reload window) and the name refreshes.

Thanks for sharing but curious how would this be faster than renaming it directly in session_index.jsonl? You would have to open that file to find the thread id, and type more characters than just the New Name, isn't it?

* For some reason not all sessions are in ~/.codex/session_index.jsonl and are instead in ~/.codex/state_5.sqlite. This seems to be the case for older threads vs newer ones. The "hacky" workaround I found was that you can just copy the id and date to add a new entry into session_index.jsonl with a new thread_name and rename it that way.

I found that my threads were all in ~/.codex/state_5.sqlite (not in a jsonl file), so I got Codex to write export and import scripts (in ~/.local/bin/), allowing me to export -> update titles -> reimport. But the titles didn't refresh after I did Reload Extension Host, or even after doing Reload Window.

On further checking, it turned out that the thread titles might be being cached on my Windows machine (I'm using WSL) in /AppData/Roaming/Code/User/globalStorage/state.vscdb, so I got Codex to update that as well. But Reload Window still didn't cause the titles to refresh.

But in the end it seems like I still had to close and reopen all instances of VS Code entirely for the thread titles to refresh. Very annoying. But at least it's possible now.

It is not an ideal solution, but I thought I would share it. I can rename sessions by editing the ~/.codex/session_index.jsonl file, then running Developer: Restart Extension Host from the Command Palette to refresh it without restarting VS Code.

My new favorite post-it note!

Not ideal, but if you open the project folder in the Codex app, you can rename it there. Then restart VS Code and it picks up the new name. Tested on Mac OS.

Not ideal, but if you open the project folder in the Codex app, you can rename it there. Then restart VS Code and it picks up the new name. Tested on Mac OS.

How to do this in App?
I am using VSCode Codex Extension and the project folder only contains jsonl files.
No name or alias available there.

> Not ideal, but if you open the project folder in the Codex app, you can rename it there. Then restart VS Code and it picks up the new name. Tested on Mac OS. How to do this in App? I am using VSCode Codex Extension and the project folder only contains jsonl files. No name or alias available there.

These are the steps I did:

1. Opened the Codex standalone app
2. Click Add new project
3. Add the VS Code project folder
4. The chat from VS Code automatically appeared
5. Select the chat
6. Click the 3 dots at the top and choose rename thread
7. Restart VS Code and it automatically picked up the new name

NO Option in Vscode Linux version to rename
no three dots

<img width="834" height="393" alt="Image" src="https://github.com/user-attachments/assets/bbfbd181-0486-47ab-b408-a25441318933" />
No Three dots option in ubuntu vscode

<img alt="Image" width="834" height="393" src="https://private-user-images.githubusercontent.com/2745267/575855439-bbfbd181-0486-47ab-b408-a25441318933.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzU3Mzk5MzEsIm5iZiI6MTc3NTczOTYzMSwicGF0aCI6Ii8yNzQ1MjY3LzU3NTg1NTQzOS1iYmZiZDE4MS0wNDg2LTQ3YWItYjQwOC1hMjU0NDEzMTg5MzMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI2MDQwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNjA0MDlUMTMwMDMxWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZTljMmFjOTZiNGE5YTIwYmFmOWY2YmI5MmMwNzgyNzhiNTczZGMyMzg5ZGY3ZWJhN2JmNGM1OWVkZmZjNWMyMCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.lejOj0VwLq17qC0rXkvrP8iZE2na5tK05_3p210EVuc"> No Three dots option in ubuntu vscode

He says open the Codex STANDALONE APP, it must be using the sync ability between Codex App and Extension, while in the App you can rename chats.

if you're not using the App, this is the best way so far:

It is not an ideal solution, but I thought I would share it. I can rename sessions by editing the ~/.codex/session_index.jsonl file, then running Developer: Restart Extension Host from the Command Palette to refresh it without restarting VS Code.

I second the motion to add renaming chats. this is ridicules . we just returned safely from the moon, to came back to not being able to rename (or any tag, flag, or metadata of any kind) is a huge disservice to our brother and sisters in the space program who want to rename chats. ridicules.

I would even be happy with /rename for now, but a right-click menu would be good, too.

This is a must-have and very core feature.

For now, for me worked to instruct Codex to name the task in the prompt in the first message.

But sometimes Codex does it wrong and then gaslights me:

<img width="800" height="338" alt="Image" src="https://github.com/user-attachments/assets/2f862493-463d-43ce-8eca-221ddaa850e8" />

ha, yeah. I tried making my first message in the chat "Title this chat XYZ", but it would always make some assumptions about what I was going to ask and make a title loosely based on that, often with the word 'update' in it.
But I would take My Awesome Task'}]}] over the crap that I've been getting.

We just need /rename 🙏🙏🙏

ha, yeah. I tried making my first message in the chat "Title this chat XYZ", but it would always make some assumptions about what I was going to ask and make a title loosely based on that, often with the word 'update' in it. But I would take My Awesome Task'}]}] over the crap that I've been getting. We just need /rename 🙏🙏🙏

Oh yeah a /rename would be incredible !
And it shouldn't be so hard to do and improved greatly the user experience !

For what it's worth I built this Codex skill based on the script from @tboen1
https://github.com/danielvik/codex_skills/tree/main/rename-thread

I've only done very limited testing, but seems to do the trick.

Thanks @danielvik, I did try your extension and couldn't get it to work. I left a couple tracker issues on your Github. Happy to work with you on getting it to work! :D
EDIT: Ah, no! I tried someone else's script for this (who also mentioned it in one of these Github issues) and _that_ one didn't work. I'll test yours, thanks for the heads-up. (P.S. Can you make it invoke from the thread using /rename?)

Please add this! It's hard to keep track of our sessions because Codex sometimes gives them weird names. If the CLI feature is already there, I would think a right click and rename to execute /rename would be a straightforward UI/UX feature that would benefit many.

I would also like to support this feature request.

Environment:

• Codex IDE extension version: 26.429.30905
• Editor: Visual Studio Code
• OS: Windows

Use case:
I use Codex in VS Code for larger, long-running development projects where multiple Codex chats/tasks are active in the same repository. The auto-generated titles are often too generic or become outdated as the scope changes.

Current problem:
I cannot rename the Codex chat/task title from the VS Code task list, chat header, context menu, command palette, or settings.

Why this matters:
Manual renaming would make it much easier to keep history organized, find the right session later, and separate sessions like implementation, review, backup, validation, or architecture work.

Expected behavior:
Please add a simple rename option in the VS Code extension, for example:

• Right-click task/thread → Rename
• Three-dot menu → Rename
• Pencil icon near the title
• Command Palette: Codex: Rename Current Task/Thread

The custom title should persist after restarting VS Code.

I do think this is a critical feature to have, not merely an 'enhancement' to be implemented in the future (or never), given how many people are still using the vscode + codex extension, especially for remote development through a tunnel rather than SSH. It's fine if you would like to start with an auto-summarized title for the session/conversation, but usually, those titles don't make any sense.

Codex on VS Code is dead, it was only ever an afterthought for them, and
they fully switched to standalone codex months ago.

Codex VS Code Extension is dead and not maintained. VS Code Codex is
depreciated.

On Thu, May 7, 2026 at 2:42 PM Yu-Jing Qin @.***> wrote:

shiaki left a comment (openai/codex#12564) <https://github.com/openai/codex/issues/12564#issuecomment-4401383482> I do think this is a critical feature to have, not merely an 'enhancement' to be implemented in the future (or never), given how many people are still using the vscode + codex extension, especially for remote development through a tunnel rather than SSH. It's fine if you would like to start with an auto-summarized title for the session/conversation, but usually, those titles don't make any sense. — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/12564#issuecomment-4401383482>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSWLVOCUJH3R36TVAEVVOT4ZT7LXAVCNFSM6AAAAACV4Q35AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMBRGM4DGNBYGI> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: @.***>

@morganross, what are you talking about, dude?

im talking about how they stopped caring about the extension and changed
focus to the standalone app. if there is any question in your mind about
it, we cannot have a debate about anything.

I am providing helpful useful expensive feedback and advice to potential users: steer clear. do not use the extension. 100% chance it will waste your time and money compared to alternatives.

On Thu, May 7, 2026 at 4:37 PM Dax Liniere @.***> wrote:

daxliniere left a comment (openai/codex#12564) <https://github.com/openai/codex/issues/12564#issuecomment-4401937954> @morganross <https://github.com/morganross>, what are you talking about, dude? — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/12564#issuecomment-4401937954>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSWLVOYCJN7PFQ5YRRELFT4ZUM3XAVCNFSM6AAAAACV4Q35AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMBRHEZTOOJVGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: @.***>

Time spent debugging my code vs debugging codex vs code extension grew to
1:2 before I stopped using it. Definitely the most fragile of the ide's
today.

On Thu, May 7, 2026 at 6:45 PM Morgan Ross @.***> wrote:

im talking about how they stopped caring about the extension and changed focus to the standalone app. if there is any question in your mind about it, we cannot have a debate about anything. On Thu, May 7, 2026 at 4:37 PM Dax Liniere @.***> wrote: > daxliniere left a comment (openai/codex#12564) > <https://github.com/openai/codex/issues/12564#issuecomment-4401937954> > > @morganross <https://github.com/morganross>, what are you talking about, > dude? > > — > Reply to this email directly, view it on GitHub > <https://github.com/openai/codex/issues/12564#issuecomment-4401937954>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABSWLVOYCJN7PFQ5YRRELFT4ZUM3XAVCNFSM6AAAAACV4Q35AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMBRHEZTOOJVGQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you were mentioned.Message ID: > @.***> >

@morganross Ah, so this is just your opinion. I thought so.

This is also a potentially mitigating fix for the case when you work with multiple different vscode windows:
Currently the chats are shared. so it becomes very difficult to track which auto-generated-chat-title belongs to each window.
The correct fix there is to bound the chats per window / project, but allowing rename would at least make it manageable before this is implemented.

If this specific related issue is bugging you, please upvote #17185 and comment there. Issue was just closed due to lack of interest.

There are several easy fixes, that's not the problem. this software is not
maintained. they switch development to the stand-alone app.

On Sun, May 10, 2026 at 1:18 AM Omry Yadan @.***> wrote:

omry left a comment (openai/codex#12564) <https://github.com/openai/codex/issues/12564#issuecomment-4414818672> This is also a potentially mitigating fix for the case when you work with multiple different vscode windows: Currently the chats are shared. so it becomes very difficult to track which auto-generated-chat-title belongs to each window. The correct fix there is to bound the chats per window / project, but allowing rename would at least make it manageable. — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/12564#issuecomment-4414818672>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSWLVIMI3K2M3BDZTUABOD42A3MTAVCNFSM6AAAAACV4Q35AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJUHAYTQNRXGI> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: @.***>

Sounds like a fork waiting to happen.

@morganross stop making things up and polluting this issue thread.

Its important that people stop using this extension and switch to a stand alone app if they want support for renaming chats. This extension is dead. depreciated. not maintained. The app works fine. Less features but less bugs. And the bugs in the app will continue to be reduced over time, unlike this extension, where bugs increase over time as vs code itself updates.

@daxliniere Delete your comment. Stop posting here unless you have something useful to contribute to the issue. I do hope that you continue to use the codex extention!

@morganross This app isn't even available in Linux. The VS code extension is simply a CLI wrapper with a few extra useful features. The Claude Code extension has rename. Easier to switch to that.

The VS code extension is also allowing me to use the same IDE for both Codex and Claude Code.
Telling people "You have to use a different IDE if you want to rename chats" is not serious.

@morganross:

this software is not maintained. they switch development to the stand-alone app

In the meantime:

<img width="790" height="548" alt="Image" src="https://github.com/user-attachments/assets/1fd6e43e-1e25-42a8-b1b6-d1421e17c269" />

<img width="640" alt="Image" src="https://github.com/user-attachments/assets/345cb244-d325-4ceb-90a5-54a737026cd4" />

People who want to use the app, will use the app. For many of us though, extension/CLI is much more comvenient.

As was already mentioned here a few times, VS Code extension is e.g. much more covenient when you work on remote instances, connected via a tunnel. Or when you use Claude Code, Cline, OpenCode, or whatnot in the same IDE. And that's just a few examples.

If you're not happy about the extension, simply don't use it, but please do not pollute this issue thread, you're not helping.

Please add this feature. We are required to use VSCode. It's mandatory. The inability to rename chats is, well, very very very annoying.

I feel like this change would take 5 minutes to implement....

For anyone interested, I have made a program which allows you to search, read and rename your Codex threads. It's a work in progress, but I use it 20 times a day.
https://github.com/daxliniere/VS-Codex-Thread-Tools-renamer-search

Thank you @daxliniere

This is already available in the ChatGPT app when using Codex.

Open ChatGPT, go to Codex, long-press the chat/thread in the sidebar, and select Rename. The same context menu also includes Pin, Mark as unread, and Archive.

I can confirm this on a Pro subscription, but I haven’t tested whether the same options are available on other tiers.

Perhaps but we are talking about the VSCode extension.
!Screenshot_20260521-110313.png

This is already available in the ChatGPT app when using Codex. Open ChatGPT, go to Codex, long-press the chat/thread in the sidebar, and select Rename. The same context menu also includes Pin, Mark as unread, and Archive. I can confirm this on a Pro subscription, but I haven’t tested whether the same options are available on other tiers.

@dirshaye should update the title to make it clearer but this is an issue for VSCode users, including Linux users who are locked out of an official Codex app. Currently the dropdown list of conversations only shows the auto-generated name and an "Archive" button.

<img width="621" height="256" alt="Image" src="https://github.com/user-attachments/assets/3a2cce0a-302c-4d67-8f4b-e91c903413e3" />

I took another pass through this thread and the current repo surface, and this looks like a good candidate for a very small VS Code extension MVP rather than a broad history-management redesign.

The app/CLI already support thread renaming, and the app-server protocol appears to expose a dedicated thread/name/set request. So the narrowest useful version for the VS Code extension could be just:

• Command Palette: Codex: Rename Current Thread
• thread/history context menu: Rename
• call the existing thread-name API
• refresh the visible title without requiring a full extension-host restart

That would avoid trying to solve search, pinning, project scoping, or richer metadata in the first pass. Those are all useful, but the core pain in this thread is simpler: users cannot assign a stable human name to the session they are actively using.

The app workaround is helpful for macOS/Windows users who can run the standalone app, but it does not fully cover VS Code extension workflows: Linux users, remote/tunnel development, WSL/SSH setups, and teams required to stay inside VS Code still need the extension surface to expose this basic operation.

A good acceptance test would be: rename a thread from the extension, restart VS Code, and verify the custom title is preserved and not overwritten by a later auto-generated title or app-side rename sync.

Per docs/contributing.md, I’m not opening an unsolicited PR, but this seems like a small enough feature shape to be maintainer-friendly if the extension team wants to prioritize it.

For me, the real pain is not renaming - it's the shared chat history across different projects. Renaming is an easy mitigation.
#17185 is discussing the real pain IMO. It was closed due to lack of community interest.
I already commented suggesting to send a PR to make this better, but I don't think anyone is watching.

If #17185 is bugging you too, please upvote it.

How is this still not a feature in 2026??

OpenAI claims to have the strongest AI and coding LLMs, yet it still can’t make different projects visible only to their corresponding conversations, nor can it even handle renaming a conversation. It’s honestly baffling.

Codex CLI has both /rename, and threads resuming isolation by working directory. Moreover, Codex CLI supports codex resume --all, which shows all threads from all working directories, and if you choose to resume a thread from a different directory it asks you if you want to switch that thread working directory to the current one or stay in the original one.

So the codebase for both features is already there and needs only be adapted to the VS Code extension.

It's just currently prioritized below many other feature requests when measured by upvotes.

Imagine such an small improment that can make more than 100 upvoters happy is still not prioritized by upvotes

It shouldn't even be about upvotes; it's a common-sense function that is essential for proper UX.
Furthermore, how hard can it be if I managed to make a whole standalone program to do this function, WITH CHATGPT, in about 10 minutes?

@etraut-openai I think the solution here is making the Codex VS Code Extension open source. I know you want to focus on Codex Desktop, but it doesn't even work for us Linux users. Serious engineers want to use Codex as well as this point as it seems with GPT you've finally built a serious coding model. VS Code + Linux is very common as many of us use multiple integrated tools.

This is almost certainly a very easy change that someone could have made a PR for.

If you can't maintain the VS code plugin, make it open source so others can help you.

@caseymelcher, you mean put the open in OpenAI?

@caseymelcher, you mean put the open in OpenAI?

No need to mock them. Codex is open. It's probably just bring overlooked rather than intentionally withheld?

The latest version of the Codex IDE Extension now supports renaming and archiving!

<img width="174" height="63" alt="Image" src="https://github.com/user-attachments/assets/76a85b8a-5f3f-4261-86ea-7ac2118ee7aa" />

Awesome.
@etraut-openai, can you please reopen the related #17185 to solicit more community feedback?

Amazing. Thanks @etraut-openai !!

Awesome. @etraut-openai, can you please reopen the related #17185 to solicit more community feedback?

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.

@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.

@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:
https://github.com/openai/codex/issues/17185#issuecomment-4582037042

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.

@etraut-openai I think the community has a hierarchy of needs, now that this one is satisfied you'll find significantly more interest in https://github.com/openai/codex/issues/17185

Do you prefer someone duplicate the request exactly as written, or reopen?

Thanks for the hard work!

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.

@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.

@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?

Yea bro u r right, the issue title was the problem, not your broke code

On Sat, May 30, 2026, 12:22 PM Denis Savenko @.***>
wrote:

whatsupbros left a comment (openai/codex#12564) <https://github.com/openai/codex/issues/12564#issuecomment-4584087008> @omry <https://github.com/omry>, #17185 <https://github.com/openai/codex/issues/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. @etraut-openai <https://github.com/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? — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/12564?email_source=notifications&email_token=ABSWLVMTW62FLNZFWL2TXV345MYG5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYGQYDQNZQGA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4584087008>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSWLVJ37OBZ6LNBJ7KAREL45MYG5AVCNFSM6AAAAACV4Q35AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKOBUGA4DOMBQHA> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ABSWLVNAXFXW3TI23QIL3UL45MYG5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYGQYDQNZQGA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ABSWLVPJOUTHATXL47JKZTD45MYG5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYGQYDQNZQGA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: @.***>

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:

• Auto-generate more descriptive titles from the task goal, similar to ChatGPT.
• Allow manual rename from the thread list and/or thread header.
• Persist user-edited titles across restarts and future fetch/resume operations.
• Prefer user-edited titles over future automatic title updates.
• Ideally expose search/filter over renamed titles.

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.

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.

@SoymilkWinsAgain, try this tool for now: https://github.com/daxliniere/VS-Codex-Thread-Tools-renamer-search

@SoymilkWinsAgain, @daxliniere, the feature to rename threads was already implemented some time ago, see https://github.com/openai/codex/issues/12564#issuecomment-4581084521, 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.