Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.271entry #184

Claude Code v2.1.271 ·

New relayFork option for forked agent queries

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

Group of 3 Nothing to try yet Internal Changes
JSON All of v2.1.271
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MemoryArea: what it touches
Internal ChangesKind: in v2.1.271,
In DevelopmentSection of the release

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.

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 doubtNothing has been read yet about how the tengu_extract_memories_extraction gate is currently set for this site's account, so no statement is…

See this entry in the whole of v2.1.271 →

Feedback