Feature request: Allow renaming chats in Codex for VS Code

Resolved 💬 3 comments Opened Apr 28, 2026 by AlexeyProvorov Closed Apr 28, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.422.62136

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 x64

What issue are you seeing?

Feature request: Allow renaming chats in Codex for VS Code

I use the Codex extension in Visual Studio Code and would like to request a UX improvement.

Currently, chats are created with automatically generated names, and there is no way to manually rename them. This makes it very difficult to navigate between chats, especially when there are many of them.

In development workflows, different chats are often used for different tasks, such as bug fixing, refactoring, experiments, or separate features. Without custom chat names, it is hard to quickly understand which chat belongs to which task.

Please add the ability to manually rename chats in Codex for VS Code.

This is critical for managing multiple development tasks efficiently.

What steps can reproduce the bug?

Open Visual Studio Code
Open the Codex extension
Start multiple chats for different development tasks
Observe that chat titles are automatically generated
Notice there is no option to rename chats manually

What is the expected behavior?

Users should be able to manually rename chats in the Codex extension.

Each chat should support a custom title so that developers can organize conversations by task (e.g., bugfix, refactor, feature work).

Optionally, users should be able to override or edit automatically generated names.

Additional information

This is not a bug but a UX limitation.

The lack of chat renaming becomes a major issue when working with many parallel tasks, as it makes navigation between conversations inefficient.

Adding this feature would significantly improve usability for developers using Codex in VS Code.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 4 months ago

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

#19653

Powered by Codex Action

jfrascon · 4 months ago

What I do normally (in Linux), until this feature is implemented, I go to path/to/.codex/session_index.jsonl, where the session ids are stored an change the 'thread_name'

From:
{"id":".......","thread_name":"<whatever_name>","updated_at":"....."}

To:
{"id":".......","thread_name":"MyName","updated_at":"....."}

Restart the codex cli or vscode (or what you use) and voilà

carlosmontoyamoya · 3 months ago

What I do normally (in Linux), until this feature is implemented, I go to path/to/.codex/session_index.jsonl, where the session ids are stored an change the 'thread_name' From: {"id":".......","thread_name":"<whatever_name>","updated_at":"....."} To: {"id":".......","thread_name":"MyName","updated_at":"....."} Restart the codex cli or vscode (or what you use) and voilà

That worked perfectly — thanks a lot for the solution!