{"version":"2.1.285","anchor":"rewind-now-stops-mcp-tasks-started-after-the-rewind-point","canonical_anchor":"rewind-now-stops-mcp-tasks-started-after-the-rewind-point","heading":"Rewinding a conversation stops MCP tasks started after that point","tier":"notice","area":"SDK","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/rewind-now-stops-mcp-tasks-started-after-the-rewind-point","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Rewinding a conversation stops MCP tasks started after that point\n\nRewinding through the `rewind_conversation` request now stops background MCP tasks started at or after the rewind point\n\n**Unclear.** It is not clear whether MCP background tasks are available to everyone or only when switched on remotely.\n\n**What**\n\n`rewind_conversation` is a request that programs driving Claude Code can send to take a conversation back to an earlier message. It now also stops background tasks that came from MCP servers (outside tools connected to Claude Code) if they were started at or after the point you rewind to. If stopping one fails, the rewind still goes ahead.\n\n**Why**\n\nRewinding no longer leaves those tasks running on their own for a part of the conversation that no longer exists.\n\n- Area: SDK\n- Names: `rewind_conversation`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}