Describe the bug
Describe the bug
After running /allow-all, the CLI still shows a permission dialog
("Do you want to run this command?") for every bash/shell tool call.
Steps to reproduce
- Launch
copilot
- Run
/allow-all
- Ask Copilot anything that triggers a shell command
- Permission dialog still appears for each command
Expected behavior
No prompts after /allow-all — all tools, paths, and URLs should be
pre-approved for the session.
Actual behavior
Every bash tool call still requires manual approval. /reset-allowed-tools
followed by /allow-all does not fix it.
Workaround
Use native built-in tools (view, grep, glob) instead of bash where possible.
Environment
Affected version
GitHub Copilot CLI 1.0.35.
Steps to reproduce the behavior
- Launch
copilot
- Run
/allow-all
- Ask Copilot anything that triggers a shell command
- Permission dialog still appears for each command
Expected behavior
No prompts after /allow-all — all tools, paths, and URLs should be
pre-approved for the session.
Additional context
Actual behavior
Every bash tool call still requires manual approval. /reset-allowed-tools
followed by /allow-all does not fix it.
Workaround
Use native built-in tools (view, grep, glob) instead of bash where possible.
Environment
Describe the bug
Describe the bug
After running
/allow-all, the CLI still shows a permission dialog("Do you want to run this command?") for every bash/shell tool call.
Steps to reproduce
copilot/allow-allExpected behavior
No prompts after
/allow-all— all tools, paths, and URLs should bepre-approved for the session.
Actual behavior
Every bash tool call still requires manual approval.
/reset-allowed-toolsfollowed by
/allow-alldoes not fix it.Workaround
Use native built-in tools (view, grep, glob) instead of bash where possible.
Environment
Affected version
GitHub Copilot CLI 1.0.35.
Steps to reproduce the behavior
copilot/allow-allExpected behavior
No prompts after
/allow-all— all tools, paths, and URLs should bepre-approved for the session.
Additional context
Actual behavior
Every bash tool call still requires manual approval.
/reset-allowed-toolsfollowed by
/allow-alldoes not fix it.Workaround
Use native built-in tools (view, grep, glob) instead of bash where possible.
Environment