{"version":"2.1.232","anchor":"agent-telemetry-records-whether-an-agent-is-built-in","canonical_anchor":"agent-telemetry-records-whether-an-agent-is-built-in","heading":"Agent telemetry records whether an agent is built in","tier":"internal","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/agent-telemetry-records-whether-an-agent-is-built-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Agent telemetry records whether an agent is built in\n\nSubagent records mark built-in agents, such as the web-fetch agent, apart from ones you wrote.\n\n**What**\n\nSubagent launch records now carry an `isBuiltIn` flag alongside the existing fork, worktree path and working directory fields, so built-in agents such as the new web-fetch agent can be told apart from ones you defined.\n\n**Details**\n\n- The built-in check moved from an inline comparison against a `\"built-in\"` source string to a shared predicate.\n- The field is only included when it is set.\n\n**Evidence**\n\n`...(n.isBuiltIn !== void 0 && { isBuiltIn: n.isBuiltIn }),`, `isBuiltIn`\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}