[BUG] "Failed to save changes" error when enabling unrestricted git push permission
Open 💬 1 comment Opened Jun 25, 2026 by kumbeechoi
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?
Environment:
- Platform: Claude.ai (web)
- Repository: kumbeechoi/alpaca-trader
- Date: June 24, 2026
Description:
When attempting to enable the "Allow unrestricted git push" permission for a connected GitHub repository in Claude's Settings → Permissions panel, the UI displays a "Failed to save changes. You can try again." error and the change does not persist.
Expected Behavior:
The permission is saved successfully and the toggle remains enabled.
Additional Context:
- The repository appears correctly connected and the toggle is visible
- The warning about elevated permissions and protected branches is displayed as expected
- Retrying does not resolve the issue
- No specific error code or network error is surfaced to the user
Attempted Workarounds:
- Retrying the save (no effect)
- (Pending) Disconnecting and reconnecting the GitHub integration
What Should Happen?
It should let me save the routine with changed permissions setting.
Error Messages/Logs
A red error message appears: "Failed to save changes. You can try again." The permission change is not saved.
Steps to Reproduce
Steps to Reproduce:
- Open Claude.ai Settings
- Navigate to the Permissions tab
- Locate the connected repository (kumbeechoi/alpaca-trader)
- Toggle on "Allow unrestricted git push — Let the agent push to any branch on this repo, including the default branch"
- Click Save
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude Code 2.1.191, running on model claude-sonnet-4-6
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗