{"version":"2.1.273","anchor":"teleport-relay-extended-to-forked-subagent-queries","canonical_anchor":"teleport-relay-extended-to-forked-subagent-queries","heading":"Teleport relay extended to forked (subagent) queries","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/teleport-relay-extended-to-forked-subagent-queries","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Teleport relay extended to forked (subagent) queries\n\nThe teleport relay mechanism now also handles forked (subagent) queries, not just the main thread\n\n**Unclear.** What the teleport relay does for the user, and what leaving or staying off it changes in practice, is not stated in the finding.\n\n**What**\n\nClaude Code has a \"teleport relay\" dispatch mechanism that previously only served queries on the main conversation thread. It now has a dedicated branch for forked queries (used by subagents), which checks whether a fork's existing context and tools are unchanged since an earlier relay decision was made, and logs when a fork's request has to leave the relay or is deliberately kept off it.\n\n**Why**\n\nThis extends the relay mechanism's reach to subagent queries, though the finding doesn't specify what the relay itself accomplishes for the user.\n\n- Flag `tengu_wild_tome`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.273; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}