Roadmap generation fails with exit code 1 when .claude/settings.local.json has restrictive Bash permissions
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?
Auto-Claude's roadmap generation (and likely other features) fails with "exit code 1" when the user's project has a .claude/settings.local.json file with restrictive Bash permissions.
What Should Happen?
Auto-Claude should either:
- Document that .claude/settings.local.json must include "Bash" (unrestricted) for Auto-Claude to work
- Or Auto-Claude's .claude_settings.json should take precedence over local settings
- Or Auto-Claude should detect conflicting permissions and warn the user
Workaround:
Add "Bash" to the allow list in .claude/settings.local.json:
{
"permissions": {
"allow": [
"Bash"
]
}
}
Error Messages/Logs
Steps to Reproduce
- Create a .claude/settings.local.json in your project with restrictive permissions:
{
"permissions": {
"allow": [
"Bash(npm:*)",
"Bash(git:*)"
]
}
}
- Run "Generate Roadmap" from Auto-Claude
- Observe "Generation Failed" with exit code 1
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.14
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
Auto-Claude writes its own settings to .claude_settings.json with "Bash(*)" permissions. However, Claude CLI also reads .claude/settings.local.json and merges settings. If the user's local settings have restrictive Bash rules (e.g., specific command patterns), those restrictions override Auto-Claude's broader permissions, causing the agent to fail when it tries to run bash commands.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗