Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.318entry #42

Claude Code v2.1.318 ·

MCP config write errors now suggest waiting longer for a locked file

If adding or removing an MCP server can't save the config, the error now blames a lock and suggests CLAUDE_CODE_CONFIG_LOCK_WAIT_MS=60000

Use it now Notable No documentation found Improvements
JSON All of v2.1.318
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.318,
What probably matters to youSection of the release
What

MCP servers are outside tools you connect to Claude Code. Adding or removing one saves the change to Claude Code's global configuration file. When that save fails, the error message now explains that other running Claude Code processes may have kept the file locked. It suggests setting CLAUDE_CODE_CONFIG_LOCK_WAIT_MS=60000, an environment variable that makes Claude Code wait up to a minute for the file to come free.

Before, the message only said to make the file writable or to run outside the sandbox.

Why

If you run several Claude Code sessions at once, they can get in each other's way when saving this file. The message now points to a setting that may get the save through.

Read from
Names in the bundleCLAUDE_CODE_CONFIG_LOCK_WAIT_MS
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_CONFIG_LOCK_WAIT_MS

See this entry in the whole of v2.1.318 →

Feedback