Describe the feature or problem you'd like to solve
No response
Proposed solution
Currently you can only set allow-all to allow the agent to execute commands without permission. Otherwise with every new session i have to approve every command over and over again.
The --allow-all flag bypasses all permission checks, which create real risks:
- Destructive commands like" rm-rf" could be e executed without confirmation
- Permission changes (chmod, chown) could silently alteer system security
A granular allowlist ( eg allow read, find, cat,ls but block rm, chmod, would provide a much better balance between autonomy and safety.
This should be configurable via instruction or agent files
Example prompts or workflows
No response
Additional context
No response
Describe the feature or problem you'd like to solve
No response
Proposed solution
Currently you can only set allow-all to allow the agent to execute commands without permission. Otherwise with every new session i have to approve every command over and over again.
The --allow-all flag bypasses all permission checks, which create real risks:
A granular allowlist ( eg allow read, find, cat,ls but block rm, chmod, would provide a much better balance between autonomy and safety.
This should be configurable via instruction or agent files
Example prompts or workflows
No response
Additional context
No response