Codex desktop: supported handling of the 64,000-byte strict auto-review limit
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Codex App version
26.903.8094.0 — verified from the Windows package manifest of the running Codex installation.
Subscription
Pro x20.
Platform
Windows x64.
What issue are you seeing?
A submission to mcp__node_repl__js was rejected with:
JavaScript execution exceeds the 64000-byte strict auto-review limit
The JavaScript submission contained 250,753 ASCII bytes. The underlying locally static-reviewed source artifacts totaled 164,692 raw bytes; the submission also included encoded inputs and invocation code.
No controller receipt, runtime output, or fixture results were returned. No retry or workaround has been attempted.
Observed steps
- Prepare the validation source and inputs.
- Submit the JavaScript payload through
mcp__node_repl__js. - Receive the error above.
Expected behavior / clarification requested
Please clarify:
- Is this limit expected?
- Does the desktop
/approvecommand apply to this specific rejection? - What supported workflow handles larger source inputs while preserving complete executable-content review?
Additional information
Feedback ID shown by the desktop app after submission:
01a08565-1735-7a13-8de8-4ff4d958401d
No source code or log attachments are included in this issue.
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 with the mcp__node_repl__js submission entry point and the desktop /approve command mentioned in the report. No source files, tests, or logs are provided, so trace how the 64,000-byte rejection is handled and determine what supported behavior and larger-input workflow should be documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- desktop-dev, devtools, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100