[macOS Desktop] A single Codex task permanently enters systemError and in-app feedback also fails with “Bad Request”
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Codex version
- ChatGPT desktop app: 26.818.41509
- Bundled Codex: codex-cli 0.149.0-alpha.4.1
- Platform: macOS
Issue
A single Codex task entered a permanent systemError state. Every subsequent message returns:
{"detail":"Bad Request"}
The task cannot recover after restarting or sending short messages. The in-app feedback action also fails, so I cannot generate or submit a feedback session ID from the affected task.
Affected task ID:
01a024fe-b891-70b2-8e05-656d2c22d36f
Steps to reproduce
- Run a long Swift/iOS development task involving file edits, simulator screenshots, and tool output.
- The task eventually returns
{"detail":"Bad Request"}. - Send a short follow-up message such as “网络问题?” or “刷新”.
- The same error is returned immediately.
- Try to submit feedback from the affected task.
- Feedback submission also fails.
Expected behavior
The task should either continue normally or provide a recoverable error with a working feedback/reporting mechanism.
Actual behavior
The affected task remains permanently unusable. Other Codex tasks in the same desktop app continue working normally.
Additional information
- Local source-code changes from the task were preserved.
- No build or shell process remained running after the failure.
- The local session transcript had grown to approximately 53 MB and contained substantial embedded screenshot/tool output.
- The task was still below the model context-window limit, so this appears more consistent with a task-state serialization or backend request-validation failure than a normal context overflow. This is an inference, not a confirmed root cause.
- Screenshot attached.
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
Start by reproducing the failure in the macOS desktop app with a long Swift/iOS task containing screenshots and tool output, then inspect the affected task and its approximately 53 MB transcript. Done means the task recovers or reports a usable error, and the in-app feedback action successfully submits a report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, macos, rust, swift
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100