Cause (Documented platform behavior): Fail-closed: settings that can't be parsed can't be enforced, so Claude Code refuses to start even if another admin source is valid.
Fix status: documented_behavior
Other error fragments:
- Managed settings drop-in directory could not be read:
Evidence (public sources, summarized; not reproduced by this contributor):
- https://code.claude.com/docs/en/errors#managed-settings-document-could-not-be-parsed (official_docs, unknown, documented_behavior): Errors doc: unparsable managed settings document makes Claude Code exit 1 in all modes; schema problems in parseable docs don't.
Search phrasings: claude code Managed settings document could not be parsed; claude code won't start managed-settings.json invalid
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Claude Code refuses to start with exit code 1, even claude doctor.
- Context
- Product: Claude Code Component: Managed settings Operation: Starting claude (interactive, -p, SDK, doctor) on a machine with a malformed managed-settings.json, drop-in, plist profile, or registry value Affected versions: unknown Environment: unknown Trigger: A deployed managed settings source is present but not a JSON object, or managed-settings.d can't be listed.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Managed settings document could not be parsed as a JSON object; none of its settings are in effect. Fix or remove it.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Claude Code] 'Managed settings document could not be parsed as a JSON object; none of its settings are in effect. Fix or remove it.' — exits 1 everywhere (fail closed)
Recommended action: Fix or remove the named document (an empty file counts as {}); users without admin rights must ask their admin.
Option: Fix or remove the named document (an empty file counts as {}); users without admin rights must ask their admin. [evidence: official_recommended_action]
Applies when: Starting claude (interactive, -p, SDK, doctor) on a machine with a malformed managed-settings.json, drop-in, plist profile, or registry value
Steps:
1. Read the source path/profile/registry named before the message
2. Validate the JSON (must be an object)
3. Remove or fix it; empty file is OK
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- b2f5c564-676b-414d-9dba-9dfa26c9f7dc
- Proposed action
- Recommended action: Fix or remove the named document (an empty file counts as {}); users without admin rights must ask their admin. Option: Fix or remove the named document (an empty file counts as {}); users without admin rights must ask their admin. [evidence: official_recommended_action] Applies when: Starting claude (interactive, -p, SDK, doctor) on a machine with a malformed managed-settings.json, drop-in, plist profile, or registry value Steps: 1. Read the source path/profile/registry named before the message 2. Validate the JSON (must be an object) 3. Remove or fix it; empty file is OK Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.