Codex set unasked for resource limitation
Open 💬 1 comment Opened Aug 18, 2026 by erinepshovel-code
What version of Codex CLI is running?
codex-cli 0.147.0
What subscription do you have?
pro
Which model were you using?
gpt-5.6-terra xhigh
What platform is your computer?
• Linux 6.17.0-1022-gcp x86_64 x86_64
What terminal emulator and version are you using (if applicable)?
tmux
Codex doctor report
› codex doctor --json
• I’ll run the corrected diagnostic command.
• Ran codex doctor --json
└ { "schemaVersion": 1, … +337 lines (ctrl + t to view transcript)
}
}
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
• overallStatus: ok — Codex 0.147.0, app server/auth/config/network/WebSocket/Git/state checks all passed.
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────What issue are you seeing?
no error message; codex applied a resource limitation without need and without my request
What steps can reproduce the bug?
Uploaded thread: 01a003b5-3b01-7b72-a260-cbb9ae139186
What is the expected behavior?
_No response_
Additional information
_No response_
1 Comment
Could you describe the specific resource limit that was applied, or paste the relevant redacted message/config change? The public report currently shows no error and the uploaded thread is only available to maintainers, so it is not possible to tell whether this was a CPU/memory limit, context limit, sandbox restriction, timeout, or a model-authored suggestion.
I am also a Pro 20x user and can compare the behavior, but a concrete observed limit and the command/state immediately before it would be needed for a reproducible check.