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.273 ·

'Teleport relay' fork-safety refinements: forkDirectLines and tools-baseline fingerprint

The prompt-cache "teleport relay" path for forked sessions gains new bookkeeping to track fork safety

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaSessionswhat it touches
KindInternal Changesin v2.1.273,
Under the hood

The prompt-cache "teleport relay" path for forked sessions gains new bookkeeping to track fork safety

What

Claude Code has an internal "teleport relay" mechanism related to prompt caching (a way of reusing previously processed prompt content to save time and cost) that comes into play when a session is forked. New bookkeeping was added to it:

  • A boot-time check arms or disables the relay based on whether a cache marker is present, logging a message like "prompt-cache relay stays off: boot had no marker" and firing telemetry events upgrade_teleport_cache and cli_teleport_arm_verdict.
  • Tracking of which forked request lines went "direct" (bypassing the relay), so later requests on the same fork skip the relay too.
  • A comparison of a captured tools baseline's model and fingerprint, to determine whether a forked request's tool set is still "intact" or has "changed".
Why

These are internal safety checks that help Claude Code decide when it's safe to reuse cached prompt state across a forked session versus when the tools or setup have changed enough that it needs to start fresh.

See this entry in the whole of v2.1.273 →

Feedback