{"version":"2.1.305","anchor":"journal-appends-serialized-mcp-host-set-servers-kept-over-s","canonical_anchor":"journal-appends-serialized-mcp-host-set-servers-kept-over-s","heading":"Session journal writes no longer overlap, and host-set MCP servers win name clashes","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/journal-appends-serialized-mcp-host-set-servers-kept-over-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Session journal writes no longer overlap, and host-set MCP servers win name clashes\n\nWrites to the local session journal now happen one at a time, and a host-set MCP server is kept over a settings one with the same name\n\n**What**\n\nThe local journal that Claude Code writes session records to now takes a lock before adding records, so two writes at the same moment can no longer mix together.\n\nSeparately, when an MCP server (a connected tool provider) set by the host program running Claude Code has the same name as one in your settings, the host-set server is kept and a message is logged. Before, the rule only looked at whether the server was of the SDK type.\n\n**Why**\n\nThis prevents torn or interleaved entries in the journal, and makes it clear which of two same-named MCP servers is used.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}