Skip to content

docs: clarify that piped commands need separate permission entries#31543

Open
jasi381 wants to merge 1 commit intoanthropics:mainfrom
jasi381:fix/docs-piped-command-permissions-31498
Open

docs: clarify that piped commands need separate permission entries#31543
jasi381 wants to merge 1 commit intoanthropics:mainfrom
jasi381:fix/docs-piped-command-permissions-31498

Conversation

@jasi381
Copy link
Copy Markdown

@jasi381 jasi381 commented Mar 6, 2026

Summary

  • Adds a tip in examples/settings/README.md explaining that each command in a piped shell expression (e.g. printf ... | msmtp -t) must have its own allow entry
  • Includes a JSON example showing the correct format
  • Notes that the same applies to &&, ||, and ; operators

Fixes #31498

Test plan

  • Verify the markdown renders correctly on GitHub
  • Confirm the JSON example in the tip is valid

Adds a tip in the settings examples README explaining that each command
in a piped shell expression (e.g. `printf ... | msmtp -t`) must have its
own `allow` entry. A single entry like `Bash(printf:* | msmtp:*)` does
not work — each command needs to be individually allowed.

Fixes anthropics#31498
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: settings.json permissions don't explain that piped commands need separate entries

1 participant