Skip to content

Assisted permissions regression #5066

Done
Done

Description

@rynoV

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

Activity

  1. added theissue type on Oct 6, 2026
  2. Tak2121 commented on Oct 6, 2026

    @Tak2121
  3. Tak2121 commented on Oct 6, 2026

    @Tak2121
  4. rynoV commented on Oct 6, 2026

    @rynoV
    Author

    Another example:

    git --no-pager diff -U2 -- Routes | Select-String -NotMatch 
    '^(diff|index|\+\+\+)' | ForEach-Object { $_.Line }
    
  5. added
    area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictions
    and removed on Oct 7, 2026
  6. thedoc31 commented on Nov 13, 2026

    @thedoc31

    We are seeing similar excessive approval requests in a VS Code-hosted Copilot SDK session.

    Environment

    • VS Code 1.146.0, stable
    • VS Code commit: 69047191fc427f2f92828279aae1d90d8eeda7ab
    • Session-reported Copilot runtime: 1.0.108-0
    • Bundled @github/copilot-sdk-darwin-arm64 package: 1.0.30-preview.0
    • macOS 27.2, arm64
    • Assisted permissions, interactive agent mode

    Observed behavior

    The assistant proposed edits to an explicit list of files, including:

    /Users/example/examplepath/src/main/java/example/ExampleService.java
    /Users/example/examplepath/src/test/java/example/ExampleServiceTest.java
    

    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.

  7. self-assigned this
    on Nov 18, 2026
  8. szabta89 commented on Nov 20, 2026

    @szabta89

    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 Name
    • git --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 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.

    Closing as fixed in 1.0.109.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:permissionsTool approval, security boundaries, sandbox mode, and directory restrictions

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions