{"version":"2.1.295","anchor":"cloud-session-pinning-and-group-changes-are-written-but-swit","canonical_anchor":"cloud-session-pinning-and-group-changes-are-written-but-swit","heading":"Trying to pin a cloud session now shows a different refusal message","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/cloud-session-pinning-and-group-changes-are-written-but-swit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Trying to pin a cloud session now shows a different refusal message\n\nPinning a cloud session now says \"Can't pin a session that's running in another terminal\"; cloud pinning and grouping are not switched on yet\n\n**What**\n\nIn the agents view, which lists your running sessions, pinning keeps a session at the top of the list. Pinning a session that Claude Code cannot manage from there is still refused, but the message has changed. Every such case now shows \"Can't pin a session that's running in another terminal\". Cloud sessions (sessions running on remote machines) used to show \"Can't pin a cloud session\" and now show the same new message.\n\nClaude Code now also has code to pin cloud sessions and to assign, rename or delete their groups. That code is switched off inside Claude Code and does not run.\n\n**Why**\n\nTo you, the only change is the new wording when you try to pin a cloud session. The code that is switched off is preparation for managing cloud sessions from this view.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}