Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.271 ·

New relayFork option for forked agent queries

← All of v2.1.271 Home All releases

Forked-agent queries, including memory extraction, can now run in a new relayFork mode, off by default

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaSubagentswhat it touches
KindInternal Changesin v2.1.271,
Group of 3 Under the hood

Forked-agent queries, including memory extraction, can now run in a new relayFork mode, off by default

What

  • 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.
  • 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.
  • The gate reads a feature flag (tengu_wild_tome), so relayFork is off by default.

Why

This 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat relayFork controls or enables is not stated in the finding.

See this entry in the whole of v2.1.271 →

Feedback