openai / openai/codex

Why so buggy?

Open
#43,036 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug extension remote windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the IDE extension are you using?

openai.chatgpt 26.901.22334 sometimes with Remote SSH

What subscription do you have?

Pro

Which IDE are you using?

VS Code

What platform is your computer?

Darwin 25.5.0 arm64 arm FROM Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?
  • Disappearing content
  • Buggy Undo/Redo behavior
  • Buggy formatted-text pasting (formatting is undesirable, but ctrl-shift-v for plaintext doesn't work either)
  • Annotation content lost on window blur (when gathering some detail from another window)
  • UI gradient fade bugs
  • Some bugs related specifically to use with Remote SSH VSCode (Windows to Mac)

It's baffling how, despite these frustrating bugs, I believe we're making good software together and that bugs in my software get fixed and don't regress - and yet this seemingly fairly simple UI extension (wrapping not-so-simple LLM stuff, but that's unrelated) has so many persistent or recurring bugs.

I list the above bugs not as a dump of individual bugs that ought to be split apart - I assume these bugs are obvious and have been noted internally or reported by others. This is more of a meta-issue wondering why the quality of this extension is as poor as it is and as a warning of discontent from a small-time but paying customer that this little corner of the openai empire is not appearing to keep pace with the rest.

What steps can reproduce the bug?

I list the above bugs not as a dump of individual bugs that ought to be split apart - I assume these bugs are obvious and have been noted internally or reported by others. This is more of a meta-issue wondering why the quality of this extension is as poor as it is and as a warning of discontent from a small-time but paying customer that this little corner of the openai empire is not appearing to keep pace with the rest.

What is the expected behavior?

I list the above bugs not as a dump of individual bugs that ought to be split apart - I assume these bugs are obvious and have been noted internally or reported by others. This is more of a meta-issue wondering why the quality of this extension is as poor as it is and as a warning of discontent from a small-time but paying customer that this little corner of the openai empire is not appearing to keep pace with the rest.

Additional information

I list the above bugs not as a dump of individual bugs that ought to be split apart - I assume these bugs are obvious and have been noted internally or reported by others. This is more of a meta-issue wondering why the quality of this extension is as poor as it is and as a warning of discontent from a small-time but paying customer that this little corner of the openai empire is not appearing to keep pace with the rest.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or reproducible entry point are provided; start by separating the listed symptoms into individual reports for the VS Code extension, including the Remote SSH setup. Each resulting issue should document exact reproduction steps and expected behavior before implementation can be assessed.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
devtools
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.