Skip to content

[Bug]: Claude reports turn/setPermissionMode failed if organisation has "full access" disabled #11068

Closed as not planned
Closed as not planned
[Bug]: Claude reports turn/setPermissionMode failed if organisation has "full access" disabled#11068
Labels
bugSomething is broken or behaving incorrectly.duplicateThis issue or pull request already exists

Description

@tyteen4a03
tyteen4a03
opened on Sep 10, 2026

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

  1. Log into a Claude account that has the organisation setting permissions.disableBypassPermissionsMode: true.
  2. Create a new conversation with "Full access".
  3. The creation fails.

Expected behavior

The Full Access option should not be available for choosing.

Actual behavior

The user gets a cryptic error message.

Impact

Minor bug or occasional failure

Version or commit

No response

Environment

No response

Logs or stack traces



Screenshots, recordings, or supporting files


No response


Workaround


No response
Activity
  1. tyteen4a03
    added 
    bugSomething is broken or behaving incorrectly.
     
    needs-triageIssue needs maintainer review and initial categorization.
     on Sep 10, 2026
  2. juliusmarminge commented on Sep 10, 2026 
    @juliusmarminge
    juliusmarminge
    on Sep 10, 2026
    Member
    Duplicate of #4927 — same report: org/policy permissions.disableBypassPermissionsMode forbids bypass, but Full access is still offered and then fails (cryptic turn/setPermissionMode / session start error). Expected fix is also the same: hide/disable Full access when policy locks bypass (with a server-side downgrade as backstop).
    

    Tracking continues on #4927 (open PR #7246).
  3. juliusmarminge
    added 
    duplicateThis issue or pull request already exists
     and removed 
    needs-triageIssue needs maintainer review and initial categorization.
     on Sep 10, 2026
  4. juliusmarminge commented on Sep 10, 2026 
    @juliusmarminge
    juliusmarminge
    on Sep 10, 2026
    Member
    Closing as duplicate of #4927.
  5. juliusmarminge
    closed this as not plannedon Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Metadata
Assignees
No one assigned
    Labels
    bugSomething is broken or behaving incorrectly.duplicateThis issue or pull request already exists
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions