[BUG] Bash tool cannot start: ENOSPC when creating /sessions/.../tmp/claude-XXXX (bootstrap deadlock)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

What happened?

The bash tool fails before any command can run.
On every invocation, it tries to create a temp dir like:

/sessions/dazzling-eager-fermat/tmp/claude-XXXX

That creation fails with disk-full behavior (ENOSPC), so even echo hi cannot execute.

This creates a bootstrap deadlock:

• I cannot run bash commands
• I cannot run cleanup commands (rm, df -h, df -i)
• I cannot recover the environment from inside the session

What Should Happen?

The bash tool fails before any command can run.
On every invocation, it tries to create a temp dir like:

/sessions/dazzling-eager-fermat/tmp/claude-XXXX

That creation fails with disk-full behavior (ENOSPC), so even echo hi cannot execute.

This creates a bootstrap deadlock:

• I cannot run bash commands
• I cannot run cleanup commands (rm, df -h, df -i)
• I cannot recover the environment from inside the session

Error Messages/Logs

Steps to Reproduce

1. Open Claude Code session in this workspace.
2. Run a minimal command (e.g. echo hi).
3. Observe failure before command execution, during temp dir creation under /sessions/dazzling-eager-fermat/tmp/.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.1.4088 (7e63fd) 2026-02-23T21:25:53.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Expected behavior

Bash should start normally and execute basic commands.
Temp directory creation should succeed, or fallback behavior should allow command execution.

Actual behavior

Bash fails to initialize on every call due to temp dir creation failure (ENOSPC behavior).
No shell command can run.

Environment

• Product: Claude Code
• Workspace/session path observed: /sessions/dazzling-eager-fermat
• Date observed: 2026-02-24
• Reproducibility: 100% in this affected environment; persists across session restarts

Diagnostics already performed

• Checked workspace tree via non-bash file tools.
• No significant cleanup targets found under the session root (no node_modules, .next, .cache, dist, build).
• Mounted user folders are present, but issue appears to be VM/sandbox-level capacity (disk or inode), not repo-level artifacts.

Impact

Completely blocks all bash-dependent workflows (git, npm, test runs, scripts).

Request

Please investigate sandbox/VM provisioning for:

1. Disk capacity and inode exhaustion handling
2. Temp dir initialization path robustness
3. Why this state can persist across session restarts for the same workspace/account

Thanks.