claude-code - 💡(How to fix) Fix [MODEL] claude --resume / claude -c crashes with sandbox error on Linux even when failIfUnavailable: false is set and bwrap is installed [1 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
anthropics/claude-code#53102Fetched 2026-04-25 06:12:17
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
3
Participants
Timeline (top)
labeled ×1

Error Message

Error: sandbox required but unavailable Error: sandbox required but unavailable

Fix Action

Fix / Workaround

Workaround: Pin to 2.1.119 and set CLAUDE_CODE_AUTO_UPDATE=false.

Workaround: Pin to 2.1.119 and set CLAUDE_CODE_AUTO_UPDATE=false.

Code Example



---
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues for similar behavior reports
  • This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Claude modified files I didn't ask it to modify

What You Asked Claude to Do

Version: 2.1.120

OS: Ubuntu 24.10, running as root

Description:

Interactive resume (claude -c, claude --resume) crashes immediately with:

Error: sandbox required but unavailable
sandbox.failIfUnavailable is set — refusing to start without a
working sandbox.

This happens even when:

  1. bwrap (bubblewrap 0.10.0) is installed and fully functional
    (bwrap --unshare-all ... echo test works)
  2. sandbox.failIfUnavailable: false is set in ~/.claude/settings.json
  3. CLAUDE_CODE_FORCE_SANDBOX=0 is set in the environment

Key observations:

  • claude -p "..." (print mode) works fine — no crash
  • Only interactive mode (-c, --resume) crashes
  • The sandbox check fires in a React useEffect in the UI layer,
    before settings.json is loaded — so failIfUnavailable: false has no effect
  • Downgrading to 2.1.119 fixes the issue completely

Expected behavior: failIfUnavailable: false in settings should
prevent the crash regardless of sandbox availability. Interactive
mode should respect this setting.

Workaround: Pin to 2.1.119 and set CLAUDE_CODE_AUTO_UPDATE=false.

What Claude Actually Did

Version: 2.1.120

OS: Ubuntu 24.10, running as root

Description:

Interactive resume (claude -c, claude --resume) crashes immediately with:

Error: sandbox required but unavailable
sandbox.failIfUnavailable is set — refusing to start without a
working sandbox.

This happens even when:

  1. bwrap (bubblewrap 0.10.0) is installed and fully functional
    (bwrap --unshare-all ... echo test works)
  2. sandbox.failIfUnavailable: false is set in ~/.claude/settings.json
  3. CLAUDE_CODE_FORCE_SANDBOX=0 is set in the environment

Key observations:

  • claude -p "..." (print mode) works fine — no crash
  • Only interactive mode (-c, --resume) crashes
  • The sandbox check fires in a React useEffect in the UI layer,
    before settings.json is loaded — so failIfUnavailable: false has no effect
  • Downgrading to 2.1.119 fixes the issue completely

Expected behavior: failIfUnavailable: false in settings should
prevent the crash regardless of sandbox availability. Interactive
mode should respect this setting.

Workaround: Pin to 2.1.119 and set CLAUDE_CODE_AUTO_UPDATE=false.

Expected Behavior

it shoudl resume / continue

Files Affected

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

No response

Claude Model

Sonnet

Relevant Conversation

Impact

Critical - Data loss or corrupted project

Claude Code Version

2.1.120

Platform

Anthropic API

Additional Context

No response

extent analysis

TL;DR

Downgrade to version 2.1.119 to prevent the crash in interactive mode.

Guidance

  • The issue seems to be related to the sandbox check in the UI layer, which fires before settings.json is loaded, making failIfUnavailable: false ineffective.
  • Setting CLAUDE_CODE_FORCE_SANDBOX=0 in the environment and sandbox.failIfUnavailable: false in ~/.claude/settings.json does not prevent the crash.
  • The crash only occurs in interactive mode (-c, --resume) and not in print mode (-p).
  • Downgrading to version 2.1.119 fixes the issue completely.

Example

No code snippet is provided as the issue is related to the behavior of the Claude model and its configuration.

Notes

The issue is specific to version 2.1.120 and does not occur in version 2.1.119. The workaround provided in the issue description is to pin to version 2.1.119 and set CLAUDE_CODE_AUTO_UPDATE=false.

Recommendation

Apply the workaround by downgrading to version 2.1.119 and setting CLAUDE_CODE_AUTO_UPDATE=false, as this has been confirmed to fix the issue.

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…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING