The newer path for sending session events can now sign peer messages, which are messages passed between connected sessions. Each event can carry a device_attestation field, proof that it came from a trusted device. Claude Code signs a message only when all of these hold:
- a trusted-device token exists
- the
tengu_ccr_v2_send_events_cliswitch is on, which it is unless switched off remotely CLAUDE_CODE_REMOTEis not set- the session's
security_tieris "elevated"
Otherwise the message is sent unsigned. Signing problems are reported as telemetry (usage data sent back to Anthropic) under peer_send_signer. Examples include an account mismatch, no account, or a device bound elsewhere.
In readings taken before this release, that switch was on for this site's account and for an anonymous account.
This adds protection against faked peer messages in Remote Control. Sessions that are not elevated are unaffected.
tengu_ccr_v2_send_events_cli On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.314: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.314. It isn't a statement about your account. What a flag value here can and cannot tell you