{"version":"2.1.318","anchor":"mcp-config-write-error-now-points-to-claude-code-config-lock","canonical_anchor":"mcp-config-write-error-now-points-to-claude-code-config-lock","heading":"MCP config write errors now suggest waiting longer for a locked file","tier":"use","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/mcp-config-write-error-now-points-to-claude-code-config-lock","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### MCP config write errors now suggest waiting longer for a locked file\n\nIf 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\n\n**What**\n\nMCP 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.\n\nBefore, the message only said to make the file writable or to run outside the sandbox.\n\n**Why**\n\nIf 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.\n\n- Area: MCP\n- Names: `CLAUDE_CODE_CONFIG_LOCK_WAIT_MS`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}