{"version":"2.1.280","anchor":"bashtool-dispatch-now-tracks-a-per-call-offcriticalpath-s","canonical_anchor":"bashtool-dispatch-now-tracks-a-per-call-offcriticalpath-s","heading":"Bash\/tool dispatch now tracks a per-call 'offCriticalPath' status for MCP background calls","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/bashtool-dispatch-now-tracks-a-per-call-offcriticalpath-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Bash\/tool dispatch now tracks a per-call 'offCriticalPath' status for MCP background calls\n\nTool dispatch now tracks whether an MCP call is off the main critical path\n\n**What**\n\nWhen Claude Code runs a tool call (including calls to MCP servers, which let Claude use external tools), it now computes an `offCriticalPath` flag. This flag is true when the call belongs to a background agent or a task that isn't part of the main flow of work. It's passed into the MCP call's watchdog (which monitors calls for problems) and into the logic that decides whether to run things in the background automatically.\n\n**Why**\n\nKnowing whether a call is off the critical path lets Claude Code treat background work differently from work the user is actively waiting on, which can affect scheduling and monitoring behavior.\n\n- Area: MCP\n- Names: `offCriticalPath`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}