{"version":"2.1.273","anchor":"new-relayeligible-field-on-fork-agent-query-telemetry","canonical_anchor":"forked-agent-relay-eligibility-gated-by-tengu-wild-tome-def","heading":"Forked agent queries now compute and report a relayEligible flag","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-relayeligible-field-on-fork-agent-query-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Forked agent queries now compute and report a relayEligible flag\n\nForked or background agent queries now track whether they're eligible for relay, gated by tengu_wild_tome, and report it in telemetry\n\n**Unclear.** The finding does not say what the relay is used for beyond eligibility tracking, and no reading has been taken of any related gate yet.\n\n**What**\n\nWhen running a forked or background agent query, Claude Code now computes a `relayEligible` flag (`on`), which is true only when the fork has no separate agent ID, has forked context messages, keeps the same tool set as its parent, and the `tengu_wild_tome` feature flag is enabled (it's off by default).\n\n- This flag is passed into the query as `relayFork`.\n\n- It's recorded as `relayEligible` in the `tengu_fork_agent_query` telemetry event and in fork-completion telemetry.\n\n**Why**\n\nThis lays groundwork for relaying forked\/background agent queries under certain conditions, while the telemetry field lets this be tracked and rolled out safely via the `tengu_wild_tome` flag.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}