{"version":"2.1.269","anchor":"remote-agent-permission-forwarding-gains-a-bound-device-sign","canonical_anchor":"remote-agent-permission-forwarding-gains-a-bound-device-sign","heading":"Remote-agent permission forwarding gains a bound-device signer for elevated-auth recovery","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/remote-agent-permission-forwarding-gains-a-bound-device-sign","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Remote-agent permission forwarding gains a bound-device signer for elevated-auth recovery\n\nRemote-agent permission requests can now retry with a fresh device signature when auth is stale or unattested\n\n**What**\n\nWhen Claude Code running as a remote agent asks for permission to do something, it now carries a `signerForBoundDevice` function alongside the request. This function can sign a fresh device attestation (proof that the request is coming from a device already registered, or \"bound\", to the account) for the specific device handling the session.\n\nIf the permission check comes back with an error meaning the device wasn't attested (`bound_unattested`) or the session is stale and needs a relogin (`session_stale_relogin`), Claude Code now uses this signer to retry the request automatically with a fresh signature, rather than failing outright.\n\n**Why**\n\nThis lets remote-agent sessions recover on their own from certain authentication hiccups tied to device verification, instead of forcing the user to log in again by hand.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}