[BUG] Plan agent requests permission for piped commands despite allowed settings (regression of #1271)

[PaulRBerg]

What's Wrong?

The Plan agent keeps requesting permission for piped commands even when both commands are explicitly listed in the allowed permissions in settings.json.

For example, when the Plan agent tries to run:

ls -lh /Users/prb/sablier/frontend/ui/apps/landing/public/blog/*.webp | awk '{print $5, $9}'

I get a permission prompt asking me to approve the command, despite having both ls and awk already configured in my allowed permissions.

What Should Happen?

When both ls and awk are in the allowed permissions list, the Plan agent should execute piped commands like ls | awk without requesting permission. This is a regression of the fix from issue #1271.

Steps to Reproduce

1. Add both ls and awk to allowed permissions in settings.json
2. Start a Plan agent session
3. Ask the agent to analyze files using a piped command (e.g., listing files with sizes)
4. Agent attempts to run a command like ls -lh path/*.webp | awk '{print $5, $9}'
5. Permission prompt appears despite both commands being whitelisted

Is this a regression?

Yes, this worked in a previous version. This issue was previously fixed in #1271 but has regressed, specifically in the context of the Plan agent.

Related Issues

• [BUG] Respect allowed-tools when using combined / piped tool commands #1271 - Original fix for piped command permissions
• Built-in Plan agent ignores parent settings.json permissions and repeatedly prompts for pre-approved tools #10906 - Related permission handling issue

Note

This bug appears to be specific to the Plan agent context. The regression may be related to how the Plan agent processes tool permissions differently from the main agent.

[github-actions]

Found 2 possible duplicate issues:

1. Built-in Plan agent ignores parent settings.json permissions and repeatedly prompts for pre-approved tools #10906
2. [BUG] Permission request for 'xargs grep' even though settings allow 'xargs grep' #2983

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[swgee]

The same issue occurs with subagents

[AbdelrahmanHafez]

Until Anthropic introduces a fix for this, here's a workaround that should enable you to fix it in a minute.

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[dlecan]

Still an issue for me

[lucasmccomb]

Still an issue for me as well. Would love a fix for this.