{"version":"2.1.292","anchor":"background-mcp-task-cap","canonical_anchor":"background-mcp-task-cap","heading":"Sending MCP tasks to the background can be refused after too many","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/background-mcp-task-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Sending MCP tasks to the background can be refused after too many\n\nClaude Code can refuse to send an MCP task to the background, and end it, when too many were started since you last wrote\n\n**Unclear.** The limit and whether this check is switched on are not stated.\n\n**What**\n\nAn MCP task is work done by an MCP server, a program that gives Claude extra tools. Claude Code can now refuse to move such a task to the background (letting it keep running while the conversation goes on) when too many have been started since a person last wrote a message. The refused task is ended.\n\n**Why**\n\nThis guards against Claude starting background tasks over and over without anyone stepping in.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}