Thread renamer for OpenAI ChatGPT/Codex VS Code extension
Patch the installed VS Code openai.chatgpt extension so you can rename Codex threads from the UI.
Install these before using the patcher:
- VS Code
- OpenAI ChatGPT/Codex VS Code extension (
openai.chatgpt) installed - Node.js (used to run the patcher CLI)
sqlite3CLI available inPATH(used by the runtime patch for cache fallback patching)
Recommended:
git(for updating/reapplying the patcher repo)
This project modifies the installed OpenAI ChatGPT/Codex VS Code extension files on your machine.
- It patches the extension manifest/runtime/webview loader.
- It adds injected patch files used by the rename feature.
- It creates timestamped backups before writing changes.
Use verify before apply, and reapply after updating the OpenAI extension.
Rename Codex Threadcommand in the Command Palette- Right-click
Rename Threadaction in the Codex thread list - Live title updates in the open Codex UI
- Persistent rename via Codex backend rename RPC
- Cache patching fallback so stale titles do not come back
node bin/codex-thread-renamer-patch.js status
node bin/codex-thread-renamer-patch.js verify
node bin/codex-thread-renamer-patch.js applyThen restart the VS Code window or run Developer: Restart Extension Host.
After patching and reloading VS Code:
- Open the Codex sidebar.
- Rename a thread using either:
- Command Palette ->
Rename Codex Thread - Right-click a thread title ->
Rename Thread
- Command Palette ->
status- Check whether the installed extension appears patchedverify- Validate extension signatures before patchingapply- Apply the patch and write backups
Optional flags:
--extension-dir <path>- Target a specificopenai.chatgpt-*install folder--dry-run- Show what would change without writing files
- Canceling the rename prompt currently shows:
Codex rename patch: Rename cancelled.
- This is a UX issue only.
- Tracked in:
Contributions are welcome.
- You can fork the repo and open a pull request.
- You can also contribute directly with a branch and pull request if you have access.
- Please do not push directly to
main, the repo uses PR-first protection. - If you are not sure where to start, open an issue or pick an existing one:


