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

Artifact sync now reads sandbox network-egress state from relay responses

Artifact sync now reads an x-ccr-sandbox-egress header from relay responses and caches per-artifact sandbox network-egress status

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaArtifactswhat it touches
KindInternal Changesin v2.1.265,
Group of 2 Under the hood No documentation found

Artifact sync now reads an x-ccr-sandbox-egress header from relay responses and caches per-artifact sandbox network-egress status

What

  • Artifact sync's status-reason handling gains a new relay_unavailable state (with a corresponding "latched" variant), alongside the existing no_originator/subscribe_forbidden states.
  • A new x-ccr-sandbox-egress response header is now read from relay routes, with recognized values disabled, restricted, or unrestricted. The value is recorded per artifact (by slug) with a 10-minute freshness window, and is read back to decide whether sandbox network access should be reported as disabled for that artifact.

Why

This lets Claude Code reflect the actual, current sandbox network-egress restrictions for an artifact based on what the relay reports, and gives a clearer signal (relay_unavailable) when the relay itself can't be reached.

Read from
Names in the bundlex-ccr-sandbox-egress

See this entry in the whole of v2.1.265 →

Feedback