{"version":"2.1.310","anchor":"cloud-session-attach-restructured-github-proxy-status-hint","canonical_anchor":"cloud-session-attach-restructured-github-proxy-status-hint","heading":"Remote session attach and GitHub proxy error messages adjusted","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/cloud-session-attach-restructured-github-proxy-status-hint","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Remote session attach and GitHub proxy error messages adjusted\n\nRemote session attaching was reworked, the GitHub proxy error skips an unknown status link, and a redundant linked-computer notice is hidden\n\n**What**\n\nThree small changes affect how Claude Code handles sessions that run in the cloud rather than on your own computer:\n\n- Attaching to a remote session is now handled in one shared place, and if attaching fails, the error is passed on instead of being swallowed.\n\n- The GitHub proxy error message no longer tells you to check a status address when Claude Code does not know one. Before, it always pointed to a `\/__agentproxy\/status` address.\n\n- The remote worker no longer shows a notice for the cloud service's own linked-computer entry.\n\n**Why**\n\nIn practice these are small behaviour tweaks. Error messages should point only at things you can actually check, failed attaches should surface as errors, and you should see one less notice that was about the service itself rather than your setup.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}