Codex VSCode Extension issues

[matthew_muntean]

The codex vscode extension has a few ongoing issues right now, leading to lost work or unexpected results due to strange behavior.

From my understanding, bugs are intended to be reported on github (github/openai/codex) - link removed due to reasons, the topic affecting me (‘submitted prompts randomly disappear’) doesn’t seem to be addressed or recognized yet.

• steering prompts get lost and/or apply at strange times depending on the ‘state’ of thinking
  - multiroot projects not supported, leading to lost chats etc in the latest version.
  And there is no changelog yet i can find.

i’m using vscode as it should be ‘the most trodden path’ for a ide usage for codex but what’s the best path to raise up issues for vscode related work. unfortunately i’ve adapted to vscode so would like to avoid leaving it due to this. I’m wondering if vscode usage is practically ‘deprecated’ and the intention to move to other ides.

is the vscode extension not recommended at the moment?

[EricGT]

Welcome to the forum!

@matthew_muntean

what’s the best path to raise up issues for vscode related work

For issues related to the OpenAI Codex extension for Visual Studio Code, the official place to report them is still the Issues tab in the OpenAI Codex GitHub repository.

I also use the Codex VS Code extension daily and report issues there from time to time.

The Codex development team uses reactions on the original GitHub issue as one signal when prioritizing work. After finding or creating the relevant issue, encouraging other affected developers to add a reaction to the original GitHub issue can help demonstrate its importance.

See:

Codex features are prioritized by votes in GitHub issues tab

FYI We prioritize feature requests based on upvotes from the community. If a feature request doesn’t get enough upvotes, we’ll close it. It’s therefore important for a feature request to have a clear and compelling title and description. We also recommend that feature requests focus on the problem statement rather than a solution. Describe the use case and what problem you’d like to see solved. There are often multiple ways to address a given problem. Source Note: In GitHub feature request…

[matthew_muntean]

Hey thanks Eric, thank you for your response.
I’ve gone and upvoted. The thumbs up convention was new to me.

It may be the ‘lost prompts’ issue was fixed in the newest version, which i’m not at the moment able to pick up, due to the ‘multiple root’ issue.

[EricGT]

@matthew_muntean

I’ve gone and upvoted.

Thank you. I do see the thumbs-up here on the forum. However, to help demonstrate support for the requested change, the thumbs-up should be added to the relevant GitHub issue rather than the forum post.

The Plan mode issue is one of the most effective examples I have seen of users coordinating their GitHub upvotes to demonstrate strong interest in a feature:

Plan Mode