codex - 💡(How to fix) Fix Improve the VS Code extension UX and interaction flow [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20116Fetched 2026-04-29 06:22:48
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×4commented ×2closed ×1
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

vscode codex plugins

What feature would you like to see?

I have a few suggestions for improving the Codex VS Code extension experience:

  1. The conversation history could be organized by project, similar to Claude Code's VS Code extension. Right now, all conversation history appears mixed together, which makes it harder to manage context across different projects.
  2. The extension menu is currently too minimal. It would be very helpful to add more menu options, especially for viewing existing MCP connections and reconnecting them directly from the UI. At the moment, if I modify an MCP configuration, I need to restart Codex before the change takes effect. This workflow could be much smoother. Claude Code's menu design could be a useful reference here.
  3. The VS Code right-click context menu could be improved. For example, if I select a few lines in the editor, the Codex extension should ideally be aware of that selection automatically, instead of requiring me to manually click "add to Codex thread" every time.
  4. Overall, I think there is still a lot of room to improve the interaction design and usability of the extension. Thank you for building and supporting this product.

Additional information

No response

extent analysis

TL;DR

The user suggests several improvements to the Codex VS Code extension, including organizing conversation history by project, enhancing the extension menu, and improving the right-click context menu.

Guidance

  • Review the existing Codex extension code to identify areas where conversation history can be organized by project, potentially using project-specific identifiers or folders.
  • Consider adding menu options for viewing and reconnecting MCP connections, and explore ways to apply configuration changes without requiring a restart.
  • Investigate how to integrate the Codex extension with the VS Code right-click context menu to automatically detect selected text and add it to a Codex thread.
  • Examine the interaction design and usability of the extension to identify areas for improvement, potentially drawing inspiration from similar extensions like Claude Code.

Notes

The provided information is focused on feature suggestions rather than a specific technical issue, so the guidance is aimed at enhancing the existing extension rather than resolving a bug.

Recommendation

Apply workaround: Implement the suggested features and improvements to enhance the user experience of the Codex VS Code extension, as they address specific pain points and areas for improvement.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Improve the VS Code extension UX and interaction flow [2 comments, 3 participants]