{"version":"2.1.311","anchor":"cloud-attach-passes-a-service-name-and-artifacts-related-tag","canonical_anchor":"cloud-attach-passes-a-service-name-and-artifacts-related-tag","heading":"Attaching to a remote session now sends a service name and device token","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/cloud-attach-passes-a-service-name-and-artifacts-related-tag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Attaching to a remote session now sends a service name and device token\n\nWhen you attach to a remote session, Claude Code now passes a service name taken from the session title and an access token for your device\n\n**What**\n\nWhen you attach to a remote session (a Claude Code session running on another machine rather than your own), Claude Code now passes along two extra things:\n\n- a service name, taken from the session's title\n\n- an access token tied to your device, used for the connection to the remote session\n\n**Why**\n\nThis changes what Claude Code sends when you attach to a remote session.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}