4 people reported
All time, since Sep 28, including 3 thumbs-up on GitHub.
Excluded aws commands stay sandboxed with --profile or --endpoint-url
“An aws call is taken out of the sandbox by the aws * entry, unless it has --profile or --endpoint-url.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/1203/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
The "aws *" entry takes other aws calls out of the sandbox, such as those with --region, --output or --query.
Is this your bug?
File my report- Where
- Bash sandbox
- Versions
- 2.1.283
- Platforms
- Linux
- How bad
- Breaks a normal workflow.
Not quite your bug?
- excludedCommands ignored by sandbox9 people
- Excluded commands stay sandboxed5 people
Original reports1, newest first
- 2.1.283: sandbox.excludedCommands never unsandboxes aws calls with --profile or --endpoint-url (Linux)#97810