Clarify on-request rule shell feature limits

Document that advanced shell features are excluded from rule evaluation, and stop listing subshell boundaries as independent command segments.

Co-authored-by: Codex <noreply@openai.com>
This commit is contained in:
Dylan Hurd
2026-02-25 16:18:19 -07:00
parent 3eba5057f8
commit 2dd562b2f1

View File

@@ -5,7 +5,6 @@ Commands are run outside the sandbox if they are approved by the user, or match
- Pipes: |
- Logical operators: &&, ||
- Command separators: ;
- Subshell boundaries: (...), $(...)
Each resulting segment is evaluated independently for sandbox restrictions and approval requirements.
@@ -19,6 +18,8 @@ This is treated as two command segments:
["tee", "output.txt"]
Commands that use more advanced shell features like redirection (>, >>, <), substitutions ($(...), ...), environment variables (FOO=bar), or wildcard patterns (*, ?) will not be evaluated against rules, to limit the scope of what an approved rule allows.
## How to request escalation
IMPORTANT: To request approval to execute a command that will require escalated privileges: