Error / Message
Malformed settings.json
A syntax error in settings.json can prevent the whole file from being read, silently dropping permissions, hooks, and other configuration defined in it.
Like .mcp.json, settings.json is parsed as a single document — an invalid file doesn't degrade gracefully, it just fails to load, taking every setting in it down at once rather than only the broken part.
This is the first thing worth checking when previously-working hooks or permission rules suddenly seem to stop applying, especially right after a manual edit.
Running the file through a JSON validator catches this faster than reading through it by eye, particularly once the file has grown to cover several different settings.
Validate settings.json with a JSON linter after any manual editFrequently asked questions
What does "Malformed settings.json" mean in Claude Code?
A syntax error in settings.json can prevent the whole file from being read, silently dropping permissions, hooks, and other configuration defined in it.
How do I fix it?
Try: Validate settings.json with a JSON linter after any manual edit
Is this something to worry about?
Running the file through a JSON validator catches this faster than reading through it by eye, particularly once the file has grown to cover several different settings.
Is this covered in OG Flow Code Premium Toolkit?
Yes — Malformed settings.json and patterns like it are covered by the commands, and in higher tiers the specialist agents and guided skills, in OG Flow Code Premium Toolkit. Tiers start at $19.90.
Want the full command, hook, and template pack?
This is one pattern from the OG Flow Code toolkit. Choose the tier that fits your workflow, including Multi-Stack for six additional language stacks.
See pricing — from $19.90 once