Skip to content

Assisted Permissions mode in Enterprise Managed environments not working alongside disableBypassPermissionsMode #341390

Closed

Description

@rwoll

Given the following Enterprise Policy:

{
  "permissions": {
    "disableBypassPermissionsMode": "disable",
    "deny": [
      "Shell(rm -rf *)",
      "Read(~/.ssh/**)"
    ]
  }
}

ls isn't even making it to the LLM-as-a-Judge so its triggering an Ask dialog even when the user is in Assisted Permissions.

This looks to be a bug in the SDK/Runtime.

Actual

Neither deny matches ls
→ server deny rules activate implicit default-ask
→ managedApprovalRequired=true
→ skip the judge and ask the human 

Expected

Effective permission decision Manual Assisted
Deny Block Block; do not invoke judge
Allow Permit Permit; do not invoke judge
Explicit ask Ask user Judge first; ask user unless judge approves
Implicit default-ask Ask user Judge first; ask user unless judge approves
Existing permissions
  deny  -> block
  allow -> permit
  ask   -> Assisted judge
             approve           -> permit
             no / error / timeout -> ask user

Activity

  1. added
    bugIssue identified by VS Code Team member as probable bug
    on Oct 13, 2026
  2. added a commit that references this issue on Oct 16, 2026
    a32f4c9
  3. added this to the 1.143.0 milestone on Oct 16, 2026
  4. vs-code-engineering commented on Oct 16, 2026

    @vs-code-engineering
    Contributor

    Sharing media and context from merged PR #341889 for verification:

    Forward the SDK's derived permission prompt so an approving Assisted verdict permits a managed request once without prompting. Preserve managed one-time restrictions and sandbox safeguards.

    ls now properly goes through to the judge and deny is still respected:

    Screenshot 2026-10-15 at 5 09 19 PM

    🤖 Authored with GitHub Copilot on behalf of Ross Wollman (@rwoll).

    Source PR: #341889

  5. added
    insiders-releasedPatch has been released in VS Code Insiders
    and removed
    unreleasedPatch has not yet been released in VS Code Insiders
    on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code Insiders

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions