{"version":"2.1.268","anchor":"subagent-progress-events-now-carry-the-underlying-api-error","canonical_anchor":"subagent-progress-events-now-carry-the-underlying-api-error","heading":"Subagent progress events now carry the underlying API error kind","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/subagent-progress-events-now-carry-the-underlying-api-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Subagent progress events now carry the underlying API error kind\n\nSubagent progress events now include the specific API error kind, not just a yes\/no flag\n\n**What**\n\nWhen a subagent (a secondary Claude instance handling part of a task) reports a tool-use event that involved an API error, the event now carries an `apiErrorKind` field with the specific error value, in addition to the existing plain yes\/no `isApiError` flag.\n\n**Why**\n\nThis gives the interface and telemetry more detail about what specifically went wrong with a subagent's API call, rather than only knowing that some error occurred.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}