{"version":"2.1.317","anchor":"remote-worker-refused-switched-off-mcp-servers-writes-are-r","canonical_anchor":"remote-worker-refused-switched-off-mcp-servers-writes-are-r","heading":"Remote Control retries a refused update about switched-off MCP servers","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/remote-worker-refused-switched-off-mcp-servers-writes-are-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Remote Control retries a refused update about switched-off MCP servers\n\nIf the server refuses an update listing switched-off MCP servers, Claude Code now retries it later with growing waits\n\n**What**\n\nWhen Claude Code runs as a remote worker, it sends its state to a server, including which MCP servers (add-on tool providers) are switched off. Before, if the server refused that update, it was counted and dropped. Now it is queued again once Claude Code is idle and retried, waiting longer between each attempt.\n\nSeparately, when a flush interval for streamed output is set, a lone piece of streamed text is now held briefly instead of sent on its own.\n\n**Why**\n\nState shown through Remote Control should stay in sync more reliably.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}