[BUG] disableBypassPermissionsMode not enforced via server-managed settings on Teams plan
Resolved 💬 1 comment Opened Mar 5, 2026 by jj-kinnovis Closed Mar 30, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Description
--dangerously-skip-permissions can be used despite disableBypassPermissionsMode being set to "disable" in server-managed org settings (admin console). This was working correctly on a prior version and broke after updating to v2.1.69.
Environment
- Plan: Teams (OAuth)
- OS: macOS
- Claude Code version: 2.1.69
- Previous working version: 2.1.63
Actual behavior
Claude Code starts normally in bypass permissions mode, ignoring the server-managed setting.
Notes
- Downgrading and upgrading again does not fix the issue
- Suspect the v2.1.69 change "Added policy limit fetching for Team plan OAuth users, not just Enterprise" may have introduced a regression in how
disableBypassPermissionsModeis evaluated for Teams plans
What Should Happen?
CLI should refuse to start in bypass permissions mode and show an error, as it did on prior versions.
Error Messages/Logs
Steps to Reproduce
- Set
disableBypassPermissionsModeto"disable"in admin console (claude.ai > Admin Settings > Claude Code > Managed settings) - Confirm it was working on a prior version
- Update Claude Code to v2.1.69
- Run
claude --dangerously-skip-permissions - Claude starts in bypass mode — should be blocked
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.63
Claude Code Version
2.1.69 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Other
Additional Information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗