Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix "command failed; retry without sandbox" for every command in Codex CLI [4 comments, 3 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#19162•Fetched 2026-04-24 05:59:35
View on GitHub
Comments
4
Participants
3
Timeline
12
Reactions
0
Author
DatamineDatamine
Participants
DatamineDataminegithub-actions[bot]github-actions[bot]viyatb-oaiviyatb-oai
Timeline (top)
commented ×4labeled ×3mentioned ×2subscribed ×2

Code Example

› can you make a new file that says foo

• What filename should I use?

› foo.txt, content: bar

• I’m creating foo.txt in the repo root with the exact content you specified.
• Added foo.txt (+1 -0)
    1 +bar

  Would you like to make the following edits?

  Reason: command failed; retry without sandbox?

› 1. Yes, proceed (y)
  2. Yes, and don't ask again for these files (a)
  3. No, and tell Codex what to do differently (esc)

  Press enter to confirm or esc to cancel
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.122.0

What subscription do you have?

Pay as you go API & Business

Which model were you using?

gpt-5.4-high

What platform is your computer?

Linux 6.8.0-101-generic x86_64 x86_64

What terminal emulator and version are you using (if applicable)?

tmux

What issue are you seeing?

Ever since codex version 0.115.0, it seems like nearly every command I run that makes a file edit fails and needs to be tried again. Upon retrying without the sandbox, it works. However, having to retry most commands is disruptive to the general workflow as it prevents the agent from doing work of any reasonable length autonomously.

The last version of codex I observed working without this issue was 0.114.0, but I'm under the impression that I will no longer be able to use this (forced deprecation) by May 8, which will be an issue for me.

Related Issue Previously, other users reported it here: https://github.com/openai/codex/issues/12888

Other System Details

  • Terminal: tmux running inside konsole
  • OS: Ubuntu 24.04
  • Shell: Bash 5.2.21

What steps can reproduce the bug?

Screenshot of Behavior <img width="749" height="480" alt="Image" src="https://github.com/user-attachments/assets/9b07fbfb-2671-4ac7-bf15-450449ef8bc6" />

Transcribed:

› can you make a new file that says foo

• What filename should I use?

› foo.txt, content: bar

• I’m creating foo.txt in the repo root with the exact content you specified.
• Added foo.txt (+1 -0)
    1 +bar

  Would you like to make the following edits?

  Reason: command failed; retry without sandbox?

› 1. Yes, proceed (y)
  2. Yes, and don't ask again for these files (a)
  3. No, and tell Codex what to do differently (esc)

  Press enter to confirm or esc to cancel

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue can be temporarily mitigated by retrying commands without the sandbox, but a more permanent solution may involve waiting for a fix in a future Codex CLI version or exploring alternative workarounds.

Guidance

  • The problem seems to be related to the Codex CLI version, as it started occurring after updating to version 0.115.0.
  • Reviewing the related issue may provide more insights or potential workarounds.
  • Consider reaching out to the Codex support team to inquire about the deprecation of version 0.114.0 and potential alternatives.
  • If possible, test the command without the sandbox to see if it works as expected, as this has been reported to resolve the issue in some cases.

Notes

The exact cause of the issue is unclear, and without more information from the Codex team or further testing, it's difficult to provide a definitive solution.

Recommendation

Apply workaround: given the information provided, retrying commands without the sandbox seems to be the most straightforward temporary solution, although it's disruptive to the workflow.

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…
#api#ssr#installation#tensor shape#request timeout

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 "command failed; retry without sandbox" for every command in Codex CLI [4 comments, 3 participants]