fix(claude): restore .claude/settings.json $schema URL#55
Conversation
The $schema value pointed at claude-code-config.json (an invalid URL in the json.schemastore.org registry). Claude Code rejects any value other than claude-code-settings.json, prints a banner, and silently ignores every permission rule in the file. This is the same regression PR #51 fixed once before; PR #48's compliance-alignment sweep reintroduced the wrong slug, likely from an upstream audit template that has not been updated yet. Refs: project memory entry feedback_claude_settings_schema_url.md. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 40 minutes and 3 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
There was a problem hiding this comment.
Pull request overview
Restores the correct $schema URL in .claude/settings.json so Claude Code recognizes and loads the settings file (ensuring permission rules in the file are applied rather than silently ignored).
Changes:
- Update
.claude/settings.json$schemafromclaude-code-config.jsontoclaude-code-settings.jsonto match Claude Code’s strict allowlist.
|



Problem
Claude Code refuses to load
.claude/settings.jsonand prints:The file's
\$schemapointed atclaude-code-config.jsoninstead of the requiredclaude-code-settings.json. Claude Code does not fail closed on this mismatch; it just shows the banner and ignores every permission rule in the file.Fix
One-line change:
claude-code-config.json→claude-code-settings.json.History
This is the same defect that PR #51 fixed previously. PR #48's compliance-alignment sweep reintroduced the wrong slug, likely because an upstream audit template still ships the bad URL.
Verification
python3 -c \"import json; json.load(open('.claude/settings.json'))\"— valid JSONpre-commit run --files .claude/settings.json— all hooks passRefs: project memory
feedback_claude_settings_schema_url.md.🤖 Generated with Claude Code