-
Notifications
You must be signed in to change notification settings - Fork 13k
Improve the VS Code extension UX and interaction flow #20116
Copy link
Copy link
Closed
Labels
enhancementNew feature or requestNew feature or requestextensionIssues related to the VS Code extensionIssues related to the VS Code extensionmcpIssues related to the use of model context protocol (MCP) serversIssues related to the use of model context protocol (MCP) serverssessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestextensionIssues related to the VS Code extensionIssues related to the VS Code extensionmcpIssues related to the use of model context protocol (MCP) serversIssues related to the use of model context protocol (MCP) serverssessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving
Type
Fields
Give feedbackNo fields configured for issues without a type.
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:
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.
Codex extension should ideally be aware of that selection automatically, instead of requiring me to manually click "add to Codex thread" every time.
Thank you for building and supporting this product.
Additional information
No response