settings.json validator
Check syntax, scope placement, exact allow/deny conflicts, and likely precedence causes. No upload required.
You have three options to validate a settings.json file, each with a different trade-off.
/status shows active settings layers, /doctor checks setup and invalid settings, and /permissions shows resolved rules and source files.python3 -m json.tool checks strict JSON syntax. The published schema at json.schemastore.org/claude-code-settings.json can add editor validation and autocomplete, with documented limitations.Start with the browser diagnostic for a private, targeted check, then use /status, /doctor, and /permissions for final confirmation inside the real environment.
Browser validator example
Environment:
OS: macOS
Version: 2.1.205
Surface: Terminal
Scope: User
Path: ~/.claude/settings.json
Paste your redacted JSON → click "Run local diagnosis"Open the checker on this site, select your environment, enter the expected path and scope, and paste a redacted copy of your settings.json. The diagnostic engine runs entirely in your browser — no content is uploaded, saved, or logged.
The diagnostic checks strict JSON syntax, whether the path fits the selected scope, an exact rule duplicated across allow and deny, and common precedence or launch-context causes. It extracts only the permissions and environment-key context it needs; it does not perform complete Claude schema, unknown-key, permission-pattern, or rule-order validation.
These checks run in the real Claude Code environment and give the most authoritative picture of what it loaded.
/doctor
Current Claude Code shows a Settings Error at startup when it detects invalid settings. If you continue, use /status to identify affected files and /doctor in the session to check setup and invalid settings. From a terminal, claude doctor runs read-only diagnostics.
/statusShows the active settings layers and identifies files with settings errors. It does not attribute every resolved key to one source, so use it to confirm which layers are active.
/permissionsShows the resolved allow, ask, and deny rules and the settings file each rule came from. This is the right view for tracing a permission rule to its source.
Use these tools for an independent syntax or editor check, while keeping their limitations in view.
Run python3 -m json.tool ~/.claude/settings.json. Strict JSON prints as formatted output; malformed input produces a parse error with a line and column. This does not validate Claude-specific fields or behavior. The published Claude settings schema allows trailing commas, so a strict parser rejecting one does not by itself prove Claude Code will reject the file.
Add "$schema": "https://json.schemastore.org/ at the top of your settings file. Compatible editors can then provide field suggestions, type checks, and hover documentation.
The schema permits additional properties and can lag fields from a new CLI release, so it cannot catch every unknown or outdated key. Treat a schema warning as a prompt to compare the current settings documentation and your installed version, not automatic proof that a field is invalid.
Quick reference
| Problem | Symptom | Next check |
|----------------------------|-------------------------------|------------------------------------|
| Malformed strict JSON | Parser reports line/column | Fix syntax; recheck /status |
| Invalid settings value | Settings Error or /doctor hit | Compare current settings docs |
| Scope or precedence issue | Active value is unexpected | Inspect active layers with /status |
| Wrong location | Expected layer is not active | Move file to the documented path |
| Exact allow/deny duplicate | Deny wins for the same rule | Remove the unintended duplicate |Use the symptom to choose the next authoritative check. No single validator covers syntax, schema guidance, scope resolution, and permission behavior equally well.
Local diagnostic
No upload. No account. The browser diagnostic checks strict syntax, path and scope fit, exact allow/deny conflicts, and likely precedence or launch-context causes in this tab.
Current Claude Code shows a Settings Error when a settings file is invalid. After continuing, use /status to find affected files and /doctor to check setup and invalid settings. The terminal command claude doctor is read-only. For an independent strict JSON syntax check, run python3 -m json.tool ~/.claude/settings.json; the published schema can add editor validation but is not a complete or always-current Claude-specific validator.
Run /permissions inside Claude Code. It lists the resolved allow, ask, and deny rules along with the settings file each rule came from. This reveals whether a rule from a different scope is overriding or duplicating your intended rule. Rules are evaluated in the order deny, ask, allow, and the first matching category determines the result.
A strict JSON validator checks syntax only. A Claude settings validator may also check fields and types against the published schema, although the schema allows additional properties and can lag a new CLI release. Settings Check is a targeted browser diagnostic: it checks strict JSON syntax, path and scope fit, exact allow/deny conflicts, and common precedence or launch-context causes; it is not a complete schema or permission-pattern validator.
Yes. Settings Check runs entirely in your browser, and it does not upload or store your content. It parses the redacted JSON you provide and stops analysis if it detects secret-like values. It then checks the path and scope, an exact allow/deny conflict, and common precedence or launch-context causes locally.
Sources last reviewed August 11, 2026.