{"version":"2.1.286","anchor":"runner-and-bridge-plumbing-proxy-refusal-callback-attachme","canonical_anchor":"runner-and-bridge-plumbing-proxy-refusal-callback-attachme","heading":"Internal changes to remote sessions, plugin sync and device enrollment","tier":"internal","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/runner-and-bridge-plumbing-proxy-refusal-callback-attachme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Internal changes to remote sessions, plugin sync and device enrollment\n\nSeveral internal pieces used by remote and bridged sessions gained new options, and trusted-device enrollment now identifies its client\n\n**Unclear.** What reads these new options and what difference they make to a user is not established.\n\n**What**\n\nSeveral internal parts of Claude Code used by remote sessions changed:\n\n- sessions started by a runner can be told when a proxy refuses a connection\n\n- a request that fetches attachments ahead of time can be limited to only the ones named\n\n- pages of the plugin list being synced now record whether the list came back incomplete\n\n- enrolling a trusted device now sends a header naming the client\n\n- the connection that streams events now reports each event once it is delivered\n\n**Why**\n\nThese affect how remote and bridged sessions behave behind the scenes.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}