{"version":"2.1.275","anchor":"new-attestation-failure-reason-surfaced-to-users-unatteste","canonical_anchor":"new-attestation-failure-reason-surfaced-to-users-unatteste","heading":"Remote worker sessions gain sender attestation checks","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-attestation-failure-reason-surfaced-to-users-unatteste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Remote worker sessions gain sender attestation checks\n\nRemote\/hosted worker sessions now verify caller attestation and report a new 'unattested_request' outcome when it fails\n\n**What**\n\n- Remote\/hosted-worker session transport now tracks a `workerAttestationPolicy`, set via a new `setWorkerAttestationPolicySink` callback, and reacts when that policy reports a fault.\n\n- A new `unattested_request` outcome was added: it appears in tool-call outcome tracking alongside `unknown_call`, `no_approval`, `stale`, `queue_full`, `rate_limited`, and `duplicate_call`, and is shown to users in Remote Control\/device-linking error explanations when a machine's account requires sender attestation that the service couldn't verify.\n\n- The method that judges inbound session-channel frames (renamed from `dropsUnverifiedSessionChannelFrame` to `sessionChannelFloorVerdict`) now returns one of three outcomes, `\"passed\"`, `\"dropped\"`, or `\"refusal_rebuilt\"`, instead of a plain true\/false, and a new `judgeInboundFrame` step classifies frames against the attestation policy.\n\n**Why**\n\nThis adds a way to detect and reject remote tool calls or session frames that can't be verified as coming from an attested sender, surfacing a clear reason instead of failing silently or ambiguously.\n\n- Area: Remote Control\n- Names: `unattested_request`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}