{"version":"2.1.232","anchor":"cloud-sessions-are-told-why-they-cannot-message-a-trusted-de","canonical_anchor":"cloud-sessions-are-told-why-they-cannot-message-a-trusted-de","heading":"Cloud sessions are told why they cannot message a trusted-device peer","tier":"soon","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/cloud-sessions-are-told-why-they-cannot-message-a-trusted-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Cloud sessions are told why they cannot message a trusted-device peer\n\nCloud sessions get told outright they cannot message peers that require a trusted device.\n\n**What**\n\nSending to a Remote Control peer from a cloud session now fails immediately with an explanation that \"that session requires a trusted device, which a cloud session never has\", instead of attempting the send. This only happens when the flag `tengu_sessions_elevated_auth_enforcement` is on, which falls back to off, and your organisation enforces the `require_trusted_devices` policy.\n\n**Details**\n\n- The check fires when the session is marked remote, has no `CLAUDE_TRUSTED_DEVICE_TOKEN`, and the org policy is enforced.\n\n**Evidence**\n\n`that session requires a trusted device, which a cloud session never has`\n\n- Flag `tengu_sessions_elevated_auth_enforcement`: Gate removed from the code (read for one account on one subscription tier against v2.1.232; this account: on, anonymous baseline: on, compiled default: not a boolean we can read) 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.\n- Area: Cross-Session Messaging\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}