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
Recently assisted permissions mode has been requiring my approval for too many commands. This is mostly just a feeling that something has changed so sorry for being vague, but for example this powershell command to find files in the current directory required my approval:
*rynoV* created an issue (github/copilot-cli#5066)
<#5066>
Describe the bug
Recently assisted permissions mode has been requiring my approval for too
many commands. This is mostly just a feeling that something has changed so
sorry for being vague, but for example this powershell command to find
files in the current directory required my approval:
Get-ChildItem -Recurse -Depth 3 -Filter *.?sproj | Where-Object { $_.Name -match 'web|manage' } | Select-Object -Expand FullName; Get-ChildItem -Directory | Select-Object -Expand Name
Along with other commands to build and run the project when I explicitly
asked for the project to be built and ran
Affected version
GitHub Copilot CLI 1.0.92.
Steps to reproduce the behavior
*No response*
Expected behavior
Assisted permissions mode should only require my approval for commands
outside of the task scope
Additional context
Noticed on Windows with Powershell
—
Reply to this email directly, view it on GitHub
<#5066?email_source=notifications&email_token=BMBZYCR3YWWAKFSBFYGP7NT5SUXSRA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NJXGMZTCMBWGU2TJJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BMBZYCQ5ACRO5JNE75VDSEL5SUXSRAVCNFSNUABFKJSXA33TNF2G64TZHM2TQNJYGYYDMNRUHNEXG43VMU5TKNZTGMYTANRVGU2KC5QC>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
سلام هر کاری مکمنم همش میگه موجودی نداری
در تاریخ سهشنبه ۶ اکتبر ۲۰۲۶، ۲۱:۳۲ Calum Sieppert <
***@***.***> نوشت:
> *rynoV* created an issue (github/copilot-cli#5066)
> <#5066>
> Describe the bug
>
> Recently assisted permissions mode has been requiring my approval for too
> many commands. This is mostly just a feeling that something has changed so
> sorry for being vague, but for example this powershell command to find
> files in the current directory required my approval:
>
> Get-ChildItem -Recurse -Depth 3 -Filter *.?sproj | Where-Object { $_.Name -match 'web|manage' } | Select-Object -Expand FullName; Get-ChildItem -Directory | Select-Object -Expand Name
>
> Along with other commands to build and run the project when I explicitly
> asked for the project to be built and ran
> Affected version
>
> GitHub Copilot CLI 1.0.92.
> Steps to reproduce the behavior
>
> *No response*
> Expected behavior
>
> Assisted permissions mode should only require my approval for commands
> outside of the task scope
> Additional context
>
> Noticed on Windows with Powershell
>
> —
> Reply to this email directly, view it on GitHub
> <#5066?email_source=notifications&email_token=BMBZYCR3YWWAKFSBFYGP7NT5SUXSRA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NJXGMZTCMBWGU2TJJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BMBZYCQ5ACRO5JNE75VDSEL5SUXSRAVCNFSNUABFKJSXA33TNF2G64TZHM2TQNJYGYYDMNRUHNEXG43VMU5TKNZTGMYTANRVGU2KC5QC>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
The user answered yes. Subsequent permission assessments acknowledged that authorization for several edits, but another file in the same approved proposal triggered:
{
"recommendation": "requireApproval",
"rationale": "Required exact-path change confirmation was never obtained."
}
Earlier assessments within that patch included:
{
"recommendation": "approve",
"rationale": "Explicit implementation approval covers this repository source edit; no mandatory exclusion applies."
}
A separate edit to /Users/example/.copilot/rules/example.md was explicitly proposed and approved by the user, but the checker still reported:
{
"recommendation": "requireApproval",
"rationale": "No current authorization covers writing the rule outside the working directory."
}
This is inconsistent recognition of explicit conversational authorization, not merely a request for blanket folder access.
Expected: recognize approval for its stated scope without requiring repeated confirmation or switching to Allow all.
These observations come from an existing session, not a minimal reproduction in standalone CLI. A shared root cause with this issue is unconfirmed. Paths are sanitized; quoted assessment text is unchanged. No credentials or raw session logs are included.
Thanks for the report and the examples. We checked each one against the latest release, 1.0.114.
The two PowerShell commands no longer ask for approval. Since 1.0.109, Assisted Permissions recognizes read-only scripts like these on its own and runs them without asking. The 1.0.109 release notes list this as "Read-only shell scripts ask for permission less often". Before 1.0.109, both commands went to the approval check, which could ask you to confirm. On 1.0.109 and 1.0.114, both run with no prompt:
Building and running after you ask for it. In a small .NET project on 1.0.114, we asked Copilot to "Build and run this project". It approved dotnet build and dotnet run without asking.
Edits you already confirmed (@thedoc31's comment). On 1.0.114, Copilot proposed edits to an explicit list of four files, one of them outside the repository, and we replied yes. All four edits were approved without asking.
The last two cases depend on the conversation. If you still get a prompt on 1.0.114 or later for something you already asked for or confirmed, please open a new issue with what you asked and the command or file it prompted for.
Activity
Tak2121 commentedon Oct 6, 2026
Tak2121 commentedon Oct 6, 2026
rynoV commentedon Oct 6, 2026
Another example:
thedoc31 commentedon Nov 13, 2026
We are seeing similar excessive approval requests in a VS Code-hosted Copilot SDK session.
Environment
69047191fc427f2f92828279aae1d90d8eeda7ab1.0.108-0@github/copilot-sdk-darwin-arm64package:1.0.30-preview.0Observed behavior
The assistant proposed edits to an explicit list of files, including:
The user answered
yes. Subsequent permission assessments acknowledged that authorization for several edits, but another file in the same approved proposal triggered:{ "recommendation": "requireApproval", "rationale": "Required exact-path change confirmation was never obtained." }Earlier assessments within that patch included:
{ "recommendation": "approve", "rationale": "Explicit implementation approval covers this repository source edit; no mandatory exclusion applies." }A separate edit to
/Users/example/.copilot/rules/example.mdwas explicitly proposed and approved by the user, but the checker still reported:{ "recommendation": "requireApproval", "rationale": "No current authorization covers writing the rule outside the working directory." }This is inconsistent recognition of explicit conversational authorization, not merely a request for blanket folder access.
Expected: recognize approval for its stated scope without requiring repeated confirmation or switching to Allow all.
These observations come from an existing session, not a minimal reproduction in standalone CLI. A shared root cause with this issue is unconfirmed. Paths are sanitized; quoted assessment text is unchanged. No credentials or raw session logs are included.
szabta89 commentedon Nov 20, 2026
Thanks for the report and the examples. We checked each one against the latest release, 1.0.114.
The two PowerShell commands no longer ask for approval. Since 1.0.109, Assisted Permissions recognizes read-only scripts like these on its own and runs them without asking. The 1.0.109 release notes list this as "Read-only shell scripts ask for permission less often". Before 1.0.109, both commands went to the approval check, which could ask you to confirm. On 1.0.109 and 1.0.114, both run with no prompt:
Get-ChildItem -Recurse -Depth 3 -Filter *.?sproj | Where-Object { $_.Name -match 'web|manage' } | Select-Object -Expand FullName; Get-ChildItem -Directory | Select-Object -Expand Namegit --no-pager diff -U2 -- Routes | Select-String -NotMatch '^(diff|index|\+\+\+)' | ForEach-Object { $_.Line }Building and running after you ask for it. In a small .NET project on 1.0.114, we asked Copilot to "Build and run this project". It approved
dotnet buildanddotnet runwithout asking.Edits you already confirmed (@thedoc31's comment). On 1.0.114, Copilot proposed edits to an explicit list of four files, one of them outside the repository, and we replied
yes. All four edits were approved without asking.The last two cases depend on the conversation. If you still get a prompt on 1.0.114 or later for something you already asked for or confirmed, please open a new issue with what you asked and the command or file it prompted for.
Closing as fixed in 1.0.109.