Codex UI is empty in VS Code ext

Resolved 💬 4 comments Opened Jun 3, 2026 by websofter Closed Jun 5, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the IDE extension are you using?

1.122.1

What subscription do you have?

Pro

Which IDE are you using?

VS Code

What platform is your computer?

Ubuntu 26

What issue are you seeing?

For the past week, the empty UI bug hasn't been resolved in any update. I've tried the new stable and pre-release versions, but they're all still empty. I'm forced to roll back to versions from a week ago.

What steps can reproduce the bug?

The error doesn't appear, it's just in the extension and doesn't allow UI

<img width="878" height="1198" alt="Image" src="https://github.com/user-attachments/assets/3ac1b9fa-5911-4c5e-acf7-28a25a55ad6c" />

I to be shown.

What is the expected behavior?

I work in Ubuntu 26 OS.

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #24601
  • #25716
  • #25328

Powered by Codex Action

etraut-openai contributor · 2 months ago

Thanks for the bug report. We haven't received broad reports of this issue, so this is likely something that's related to your configuration. Let's see if we can diagnose the problem. I'd start by temporarily renaming the ~/.codex directory to something like ~/.codex-bak and then restart the extension. You'll need to log in again. If that eliminates the "UI is empty" problem, then we can dig further to determine whether it's an issue with your configuration (~/.codex/config.toml), your saved sessions, the sqlite db state that Codex maintains as a cache, or some other issue.

websofter · 2 months ago

Codex конфликтует с Amazon Q, отключение не решает, надо полностью удалить Amazon Q

timohuovinen · 1 month ago

@etraut-openai I've seen broad reports of this issue, and I'm experiencing it since june 5th