Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.321entry #83

Claude Code v2.1.321 ·

Apps that manage Claude Code's config folder survive a broken ~/.claude.json

With CLAUDE_CODE_HOST_OWNED_CONFIG_DIR set, a ~/.claude.json that cannot be read no longer stops Claude Code; it starts on defaults

You'll notice No documentation found Improvements
JSON All of v2.1.321
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SettingsArea: what it touches
ImprovementsKind: in v2.1.321,
ImprovementsSection of the release
What

When another application starts Claude Code and owns its configuration folder, it names that folder with CLAUDE_CODE_HOST_OWNED_CONFIG_DIR. In that case, if the global configuration file (~/.claude.json) cannot be read because it is damaged, Claude Code now starts with default settings and prints a notice. Before, it stopped with an error.

The next time Claude Code saves its settings, it overwrites the damaged file.

Why

Desktop apps and other programs that embed Claude Code can recover from a corrupt configuration file. Anything left in the damaged file is lost once the new save replaces it.

Read from
Names in the bundleCLAUDE_CODE_HOST_OWNED_CONFIG_DIR
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_HOST_OWNED_CONFIG_DIR

See this entry in the whole of v2.1.321 →

Feedback