{"version":"2.1.323","anchor":"mcp-task-resume-polling-constants-added","canonical_anchor":"mcp-task-resume-polling-constants-added","heading":"Groundwork for resuming MCP tasks by polling","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-task-resume-polling-constants-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Groundwork for resuming MCP tasks by polling\n\nClaude Code now contains settings for an MCP task-resume poller with an eight-day expiry, with no sign yet of how it is used\n\n**Unclear.** Nothing shows how or when this polling is used.\n\n**What**\n\nClaude Code now contains the fixed values for a poller that resumes MCP tasks. MCP (Model Context Protocol) is how Claude Code connects to outside tools. These include a request header, `X-CCR-Mcp-Poller`, a key, `com.anthropic\/mcp-poller`, and an expiry of eight days.\n\n**Why**\n\nThe names suggest MCP tasks in remote sessions may later be resumed by checking back on them at intervals.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}