macOS Desktop app returns HTTP 429 for every Chat message while Web and iOS work normally
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.810.52044
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Darwin 25.6.0 arm64 arm
What issue are you seeing?
The Chat surface in the new unified ChatGPT desktop app for macOS fails with HTTP 429 on every message.
Exact error:
Request failed with status 429
The problem occurs in both existing conversations and completely new chats, including when sending only:
test
The same OpenAI account works normally at the same time:
- in ChatGPT Web on the same Mac
- in the ChatGPT iOS app
The failure appears isolated to the macOS desktop client.
Feedback ID:
no-active-thread-01a0076b-c203-7601-8d65-80b6f65e0203
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a0076b-c203-7601-8d65-80b6f65e0203
What is the expected behavior?
- Open the new ChatGPT desktop app on macOS.
- Select ChatGPT and use the normal Chat experience.
- Start a completely new chat.
- Send the message:
test
- The app immediately returns:
Request failed with status 429
- Repeat in another new chat - the same 429 occurs.
- Fully quit the app with Cmd+Q and reopen it - still fails.
- Restart the Mac - still fails.
- Log out of the desktop app and log back in - still fails.
- Switch the Mac from the normal Internet connection to an iPhone hotspot - still fails.
- Open ChatGPT Web on the SAME Mac, using the SAME account and SAME hotspot - Web works normally.
- Test the SAME account in the ChatGPT iOS app - iOS works normally.
- Uninstall and reinstall the ChatGPT desktop application - still fails.
- Check for updates - the app reports version 26.810.52044 is currently the newest available version.
The issue is therefore reproducible only in the macOS desktop client.
Session ID:
I do not currently have a session ID exposed by the app.
Feedback ID:
no-active-thread-01a0076b-c203-7601-8d65-80b6f65e0203
Context window:
The issue reproduces in a completely new chat with only the single word "test", so it is not dependent on a large conversation context.
Token/context usage:
Exact token usage is not exposed to me for the failed Chat request.
Additional observation:
The desktop sidebar shows "Usage 0% left", but normal Chat continues to work through Web and iOS using the same account.
Additional information
This is specifically a failure of Chat inside the new unified desktop app, not a Codex coding task.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is named, and the report says this is not a Codex coding task. Start by reproducing the 429 in macOS app version 26.810.52044 using feedback ID no-active-thread-01a0076b-c203-7601-8d65-80b6f65e0203; done would mean Chat messages succeed in the desktop client while Web and iOS remain working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100