You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature Request] Per-agent permission scoping for tool restrictions #41301
Permission rules (permissions.deny/permissions.allow in settings.json) are project-level and apply uniformly to all agents, skills, and the user. There's no way to scope
permission rules to a specific agent.
Use case: I have multiple agents — an implementer agent that should be restricted from running destructive commands (cdk deploy, aws writes, git push), and other agents that
need those commands. Today I either deny at the project level (blocking myself and all agents) or rely on prompt-level instructions (advisory, not enforced).
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
Activity
github-actions commentedon Mar 31, 2026
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
github-actions commentedon Apr 3, 2026
This issue has been automatically closed as a duplicate of #16628.
If this is incorrect, please re-open this issue or create a new one.
🤖 Generated with Claude Code
github-actions commentedon Apr 11, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.