{"version":"2.1.271","anchor":"extractmemories-gains-a-relayfork-mode-via-a-new-gate","canonical_anchor":"memory-extraction-forked-query-gets-a-new-relayfork-mode","heading":"New relayFork option for forked agent queries","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/extractmemories-gains-a-relayfork-mode-via-a-new-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New relayFork option for forked agent queries\n\nForked-agent queries, including memory extraction, can now run in a new relayFork mode, off by default\n\n**Unclear.** Nothing has been read yet about how the tengu_extract_memories_extraction gate is currently set for this site's account, so no statement is made about whether relayFork is active, and what relayFork changes in extraction behavior is not described.\n\n**What**\n\n- The forked-agent execution function now accepts a new `relayFork` option and threads it into the underlying query call, alongside the existing `compactionRequestKind` and `thinkingStripPlan` options.\n\n- The memory-extraction path (`extract_memories`) sets `relayFork` based on a new gate combined with a sync check, and logs the value in telemetry as `relay_fork`.\n\n- The gate reads a feature flag (`tengu_wild_tome`), so `relayFork` is off by default.\n\n**Why**\n\nThis is internal plumbing for a new relay-based mode for forked and background queries such as memory extraction; since it's gated behind a disabled flag, it has no visible effect yet.\n\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5"}