{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifdt6arysjv75s4mwhj4ubmhb2vdafsqcr4ztn2t4zasy4k5sryaa",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3ml7zm6rdsq42"
  },
  "path": "/t/codex-vs-code-extension-needs-manual-thread-renaming/1380426#post_1",
  "publishedAt": "2026-05-06T23:18:48.000Z",
  "site": "https://community.openai.com",
  "textContent": "Hello, I want to submit a usability complaint and feature request for the Codex VS Code extension.\n\nThe current thread list is very hard to use because thread titles are auto-generated by first phrase and often too vague. After a few sessions, it becomes difficult to understand what each thread is actually about. This makes navigation and context switching unnecessarily slow.\n\nIn practice, I need a way to manually rename threads so I can give them clear project-specific names such as:\n\n  * my-project-1\n  * my-project-2\n  * my-project-1-infra\n\n\n\nRight now, in the VS Code extension, I cannot find any exposed way to rename a thread. This is a major usability gap.\n\nPlease add:\n\n  * Rename Thread in the thread context menu\n  * Rename Thread in the command palette\n  * inline title editing in the sidebar\n  * optional automatic naming based on workspace/repo name\n\n\n\nThis would make the extension much easier to use in real multi-project workflows.\n\nThank you.",
  "title": "Codex VS Code extension needs manual thread renaming"
}