Sandbox cannot be enabled on macOS: /sandbox menu unresponsive and settings.json ignored

Description

Sandbox cannot be enabled on macOS. Two separate issues prevent activation:

1. /sandbox interactive menu does not respond to keyboard input — arrow keys, Tab, and Enter have no effect. Only Escape works (to dismiss). This occurs in both Terminal.app and zsh.

1. sandbox.enabled: true in settings.json is ignored — /status does not show sandbox as enabled, even after restart.

Environment

• macOS: 26.2 (Build 25C56)
• Architecture: arm64 (Apple Silicon)
• Claude Code: v2.1.71
• Terminal: Terminal.app (also tested in zsh shell)
• Shell: bash (also tested with zsh)
• sandbox-exec: available at /usr/bin/sandbox-exec (Seatbelt)
• bubblewrap: not installed (Linux-only, not expected on macOS)

Steps to reproduce

Issue 1: /sandbox menu unresponsive

1. Start Claude Code: claude (or with custom config dir)
2. Type /sandbox
3. Menu appears showing dependencies (bubblewrap, socat, seccomp) as installed
4. Arrow keys, Tab, and Enter do nothing
5. Only Escape works (dismisses the menu)

Issue 2: settings.json sandbox config ignored

1. Add sandbox config to ~/.claude/settings.json:

``json
{
"sandbox": {
"enabled": true,
"autoAllowBashIfSandboxed": true
}
}
``

1. Also added to project-level .claude/settings.json (same config)
2. Restart Claude Code
3. Run /status
4. Expected: Sandbox shown as enabled
5. Actual: No sandbox information displayed in /status output

Notes

• The /sandbox menu shows "bubblewrap: installed", "socat: installed", "seccomp filter: installed" — but these are Linux tools. On macOS, Seatbelt should be used instead. This suggests the /sandbox UI may be checking for the wrong dependencies on macOS.
• Using CLAUDE_CONFIG_DIR to point to a custom config directory (~/.claude-sdlc/) does not change the behavior.
• The settings.json files are valid JSON (verified with Python json.load()).

Expected behavior

Either:

• The /sandbox interactive menu should respond to keyboard input on macOS Terminal.app, OR
• Setting sandbox.enabled: true in settings.json should enable the sandbox without requiring the interactive menu

Workaround

None found. The sandbox cannot be enabled on this configuration.