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

Remote sessions re-bind the event signer when security tier is raised

Remote sessions now re-key their event signer after the server escalates the security tier, instead of only binding it once

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaRemote Controlwhat it touches
KindInternal Changesin v2.1.271,
Group of 3 Under the hood

Remote sessions now re-key their event signer after the server escalates the security tier, instead of only binding it once

What

  • Remote-attach sessions' device event signer now supports rebindEventSigner(), which re-reads the session's current device binding and rebinds the signer if it changed, instead of only being set once at attach time.
  • The remote session client now handles a new security_update control frame. When it reports security_tier as elevated, the session flags that a raise was seen, and on the next reconnect it calls rebindEventSigner() to re-establish the signer under the new tier.
  • Concretely, SessionsV2Client handles this as a new SSE event type carrying security_tier; an elevated tier triggers onSecurityTierRaised, which sets securityTierRaiseSeen and causes the next reconnect to re-key the session's event signer.

Why

This keeps a remote session's cryptographic event signer in sync when the server tightens security requirements mid-session, without forcing the user to start a new session.

See this entry in the whole of v2.1.271 →