{"version":"2.1.309","anchor":"resumed-agents-launched-from-a-stream-are-treated-as-built-i","canonical_anchor":"resumed-agents-launched-from-a-stream-are-treated-as-built-i","heading":"Resumed agents started from a stream count as the built-in type","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/resumed-agents-launched-from-a-stream-are-treated-as-built-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Resumed agents started from a stream count as the built-in type\n\nWhen an agent started from a stream is resumed, Claude Code now treats it as the built-in agent type\n\n**Unclear.** It is not clear what being treated as the built-in type changes for a resumed agent.\n\n**What**\n\nAn agent is a helper Claude can start to work on part of a task. When an agent is resumed, Claude Code decides whether it is the built-in type. Agents that were launched from a stream now also count as built-in.\n\n**Why**\n\nThis is a small change to how resumed agents are handled.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}