Newst VS Code extension just makes codex flash and blink

Open 💬 11 comments Opened Apr 23, 2026 by visnetwork
💡 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?

26.5422.20832

What subscription do you have?

Plus

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

After installing the most recent release of the extension (today 2026-04-23) the Codex does not load inside VS Code, it just keeps flashing and blinking on the screen. I had to roll back to the previous version.

see screen capture
https://github.com/user-attachments/assets/e099039a-e95a-43ee-a91c-30eaf69fd8b5

What steps can reproduce the bug?

Install the current extension in VS Code 26.5422.20832

What is the expected behavior?

Load the tasks in codex

Additional information

_No response_

View original on GitHub ↗

11 Comments

github-actions[bot] contributor · 2 months ago

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

  • #19097
  • #19039
  • #18816
  • #18515

Powered by Codex Action

etraut-openai contributor · 2 months ago

Can you confirm that if you downgrade to the previous version, it works on your system? I just want to verify that it's a regression in the Codex extension rather than some configuration change that coincidentally happened around the same time on your machine.

HRussellZFAC023 · 2 months ago

<img width="1383" height="800" alt="Image" src="https://github.com/user-attachments/assets/dec90e10-8f8d-44f1-890a-e54833dd93d1" />

XuGuangnian · 2 months ago
Can you confirm that if you downgrade to the previous version, it works on your system? I just want to verify that it's a regression in the Codex extension rather than some configuration change that coincidentally happened around the same time on your machine.

yes, rolling back to version 26.5417.40842 restores normal functionality.

Environment:
VS Code with WSL (Ubuntu 24.04)

Broken versions:

26.5422.20832
26.5422.21459

Note:
The issue only occurs in WSL, it works normally on Windows.

fritzklyka · 2 months ago

I also got the same error on my mac (26.3.1 (25D2128) rolled back to version 26.5417.40842 then it works.
Later than that. It breaks.

davidacres · 2 months ago

I have the same on my mac OS 26.5 I had to rollback to 40842 same as previously mentioned.

TimothyMeadows · 2 months ago
I have the same on my mac OS 26.5 I had to rollback to 40842 same as previously mentioned.

Same here, opened my mac, updated, visually the codex extension is just refreshing onto it's self over and over totally unusable. Had to downgrade to the same version. Works fine now.

eric-rolph · 2 months ago

Unusable flicker using latest patched Windows 11, latest Nvidia display driver 5090, latest (not Insiders) version of VS Code, new Codex extension install. App has issues as well, new install, cannot make it past logo.

Edit: Oauth was causing the issue for me. A 5 day old version allowed me to get the status message:

"Your access token could not be refreshed because your refresh token was already used. Please log out and sign in again."

Fixed by by running in terminal/powershell:

codex logout
codex login
codex login status
bfil · 2 months ago

The issue seems to be the same in both the Codex app and the VSCode extension. Deleting the ~/.codex/auth.json file forced a re-authentication in both the app and the extension and it fixed my issue (on mac).

gabekao · 2 months ago

~~Chiming in. W10.0.22631 / VSCode 1.117.0, every version of the Codex extension since 40842 (not including 40842) has caused sporadic flashing. Codex CLI/Codex app not installed. Reauthorizing the extension (deleting auth.json and signing in again) doesn't alleviate the issue. Doesn't flash during the sign in process, only once authorized and trying to load the chat history, seemingly.~~

VSCode 1.118.0, Codex 26.442.71525 seems to have resolved it for me.

ctkm-aelf · 18 days ago

Reproduction notes and proposed fix path

I took a pass at reducing this to an actionable code path before suggesting a fix.

Breakdown:

  • I treated the report as reproducible enough to trace against the current code instead of asking for more information.
  • Root cause: codex-rs/code-mode-host/src/lib.rs:566
  • Impact: calibrated priority score 80.8

Proposed approach:

  • Keep the patch scoped to the code path around codex-rs/code-mode-host/src/lib.rs:566, so the behavior changes where the regression is introduced rather than broadening the surface area.
  • Validation plan: add or update focused regression coverage and run the affected package test target before proposing the branch
  • I will not open an unsolicited PR; if this direction matches maintainer expectations, I can open the prepared branch for review.

Precedent: #29189 Codex Desktop 26.616.41845 node_repl fails: codex/sandbox-state-meta missing sandboxPolicy

How I shaped this comment from prior successful threads:

  • Nearest successful examples considered: 3.
  • The shared pattern was to show the repro/root-cause evidence first, state the smallest viable fix, defer to maintainers on direction, and disclose AI assistance.

This analysis was prepared with AI assistance.

<!-- fkst:codex-saga:engage:codex-triage:dup:openai/codex#19181 -->