{"version":"2.1.307","anchor":"artifact-mcp-reads-retry-once-on-a-stale-reused-socket","canonical_anchor":"artifact-mcp-reads-retry-once-on-a-stale-reused-socket","heading":"Artifact reads retry once when an idle connection has gone stale","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/artifact-mcp-reads-retry-once-on-a-stale-reused-socket","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Artifact reads retry once when an idle connection has gone stale\n\nA read of artifacts that fails because the server already closed an old connection is now retried once on a fresh connection; writes are not retried\n\n**What**\n\nArtifacts are saved outputs that Claude Code fetches through an MCP server (an add-on service that gives Claude extra tools). To save time, Claude Code reuses one open connection for several requests. If the server had already closed that connection, a request could fail.\n\nNow, when a read-only artifact request fails for that reason, Claude Code sends it once more on a new connection. Requests that change something are not resent. The request that lists the server's tools, and the other requests to this server, now go through the same handling.\n\n**Why**\n\nThis cuts down on artifact errors that appear after Claude Code has been idle for a while.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}