[BUG] Can't change tabs in /sandbox command
Status Fixed / completed
Reported on v2.1.76
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 5 comments · opened Mar 17, 2026 · closed Apr 2, 2026
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?
When I try to configure the sandbox with /sandbox I see the following:
Sandbox: Mode Dependencies Overrides Config
Cannot block unix domain sockets (see Dependencies tab)
Configure Mode:
❯ 1. Sandbox BashTool, with auto-allow
2. Sandbox BashTool, with regular permissions
3. No Sandbox (current)
Auto-allow mode: Commands will try to run in the sandbox automatically, and attempts to run outside of the sandbox
fallback to regular permissions. Explicit ask/deny rules are always respected.
Learn more: code.claude.com/docs/en/sandboxing
But I can't switch to the "Dependencies" tab using <TAB>. It just doesn't do anything.
What Should Happen?
It should switch the tag
Error Messages/Logs
Steps to Reproduce
- Start claude
- Execute
/sandboxcommand - Try to switch tabs.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.76
Claude Code Version
2.1.77
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
Other
Additional Information
I'm using Alacritty.
5 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I think this is a regression of #31757
In the meantime, I was able to navigate between the tabs by using the up arrow to go above the options, and then use the left/right arrows / tab/shift+tab to switch between tabs. (At least for me there's no visual indication that this "selects" the tabs, other than the arrow indicating the current option in the tab content disappearing.)
Seems to be fixed again in v2.1.86
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.