Rename sandbox `excludedCommands` to `unsandboxedCommands` for clarity
Status Closed — not planned
Maintainer reply None cached
Activity 2 comments · opened Mar 25, 2026 · closed Apr 24, 2026
Problem
excludedCommands is counterintuitive. The name suggests these commands are blocked, when they actually run outside the sandbox with no restrictions.
allowUnsandboxedCommands already uses the correct mental model in the same config block. excludedCommands should follow the same convention.
Suggestion
// Current — confusing
"excludedCommands": ["git", "docker", "brew"]
// Proposed — clear
"unsandboxedCommands": ["git", "docker", "brew"]Keep excludedCommands as a deprecated alias for backwards compatibility.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗