codex - 💡(How to fix) Fix The codex application and extensions cannot be accessed [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20057Fetched 2026-04-29 06:23:23
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×2commented ×1cross-referenced ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.422.62136

What subscription do you have?

pro

What platform is your computer?

macos:Darwin 25.4.0 arm64 arm

What issue are you seeing?

Whenever I open the Codex app or the Codex extension in VS Code, it gets stuck on the loading screen. I only see the Codex icon, but it never actually loads. Strangely, it works perfectly fine on my Windows system. I've already tried reinstalling it and deleting the .codex file/folder, but nothing has worked. Deleting the .codex folder does trigger the login prompt, but once I log in, I'm back to the same endless loading screen. I've also noticed on some Chinese tech forums that other users are experiencing this exact same issue.

What steps can reproduce the bug?

open the codex app or ide extension on macos

What is the expected behavior?

it gets stuck on the loading screen. only see the Codex icon, but it never actually loads.

Additional information

The Codex login process and ChatGPT can both be accessed normally, so I think network issues can be ruled out. I also noticed that after waiting for a while on another desktop and then switching back to the Codex page, the Codex app briefly shows the page after entering, but then quickly returns to the loading screen.

extent analysis

TL;DR

The issue might be related to a compatibility problem with the Codex App on macOS, and trying a different version or configuration could help resolve the loading screen issue.

Guidance

  • Verify that the issue persists across different networks to rule out any network-specific problems, despite the user's initial assessment that network issues can be ruled out.
  • Check for any updates to the Codex App or VS Code extension, as newer versions might address compatibility issues with macOS.
  • Consider testing the Codex App or extension on a different macOS system to see if the issue is specific to the user's setup.
  • Look into the Chinese tech forums mentioned for any potential workarounds or fixes that other users have found.

Example

No specific code snippet can be provided due to the nature of the issue, which appears to be related to application compatibility rather than code.

Notes

The issue seems to be specific to macOS, as the user mentions it works fine on their Windows system. The fact that deleting the .codex folder triggers a login prompt but doesn't resolve the issue suggests a deeper compatibility or configuration problem.

Recommendation

Apply workaround: Given the information, it seems prudent to explore workarounds such as checking for updates, testing on different systems, or looking into forum discussions for temporary fixes until a more permanent solution is found.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix The codex application and extensions cannot be accessed [1 comments, 2 participants]