{"version":"2.1.319","anchor":"usage-limit-wait-surfaced-in-task-progress-and-tool-errors-c","canonical_anchor":"usage-limit-wait-surfaced-in-task-progress-and-tool-errors-c","heading":"Task progress shows usage-limit waits, and MCP tool errors carry a code","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/usage-limit-wait-surfaced-in-task-progress-and-tool-errors-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Task progress shows usage-limit waits, and MCP tool errors carry a code\n\nTask progress updates now say when a task waits on a usage limit and when it resets, and MCP tool errors now carry an error code\n\n**What**\n\nThe SDK is the toolkit for building programs on top of Claude Code. Several things it reports are different:\n\n- Task progress updates now include `usage_limit_wait`, with the time the limit resets, when a task is waiting on a usage limit.\n\n- Errors from MCP tools, which are tools provided by outside programs, now carry an `error_code`, taken from a `code` the server puts in the result's `_meta` field.\n\n- Task results can now include content that is not text.\n\n**Why**\n\nPrograms built on the SDK can show that a task is paused by a usage limit and when it will continue, and can react to specific MCP errors by their code.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}