Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.274 ·

New server_authored/server_replayed event origins normalized in bridge attestation

Remote-control bridge events can now be tagged as server_authored or server_replayed, and attestation filtering treats both the same as unspecified.

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaRemote Controlwhat it touches
KindInternal Changesin v2.1.274,
Group of 2 Under the hood

Remote-control bridge events can now be tagged as server_authored or server_replayed, and attestation filtering treats both the same as unspecified.

What

  • The function that maps event-origin strings to display values now recognizes two new values, server_authored and server_replayed, mapping them to SERVER_AUTHORED and SERVER_REPLAYED respectively.
  • When remote-control bridge events are filtered by device attestation status, events with a SERVER_AUTHORED or SERVER_REPLAYED status are now normalized to UNSPECIFIED before the accept-level/accept-status checks run.

Why This lets the bridge distinguish events that were authored or replayed by the server itself from device-attested events, while ensuring attestation filtering doesn't mistakenly treat them as attested device events.

See this entry in the whole of v2.1.274 →