{"version":"2.1.323","anchor":"remote-mcp-task-relay-over-the-session-channel","canonical_anchor":"remote-mcp-task-relay-over-the-session-channel","heading":"Remote clients can check, cancel and wait on MCP tasks through a session","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-mcp-task-relay-over-the-session-channel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote clients can check, cancel and wait on MCP tasks through a session\n\nA session can now answer remote requests to look up, cancel or wait on an MCP task, under several conditions\n\n**Unclear.** It is not clear what turns MCP tasks on, so it is not known whether this works for every user.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Some of their tools run as tasks, which are jobs that can keep going for a while. A program connected to a Claude Code session from elsewhere can now send it an MCP task request. The request can do one of these:\n\n- `tasks\/get` looks up a task\n\n- `tasks\/cancel` cancels a task\n\n- `wait` waits on a task\n\nClaude Code only serves the request when all of these hold:\n\n- the request carries a ticket\n\n- the request carries an interface version\n\n- MCP tasks are enabled\n\nThe request is refused when the tool is denied, or when the tool has `PostToolUse` hooks. A hook is a command you set up to run automatically at a certain moment, and `PostToolUse` hooks run after a tool call succeeds.\n\n**Why**\n\nThis lets a remote connection do more with tools that a session hosts, including long-running MCP tasks.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}