{"version":"2.1.314","anchor":"remote-sessions-get-a-background-task-shortcut-hint-and-a-co","canonical_anchor":"remote-sessions-get-a-background-task-shortcut-hint-and-a-co","heading":"Background shortcut now works in remote sessions, with a notice when it fails","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/remote-sessions-get-a-background-task-shortcut-hint-and-a-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Background shortcut now works in remote sessions, with a notice when it fails\n\nIn remote sessions, the background shortcut asks the session to move work to the background and shows a notice if that fails\n\n**What**\n\nA remote session is a Claude Code session running on another machine or in the cloud that you are connected to. In a remote session, the keyboard shortcut for moving work to the background now sends that request to the session, and gives up after a time limit. The hint in the footer at the bottom of the screen reads \"run in background\" in remote sessions and \"background\" everywhere else.\n\nIf the request does not go through, a notice beginning \"Couldn't move this to the background:\" gives one of three reasons:\n\n- The session didn't answer. In this case the work may still move to the background.\n\n- There was a server error.\n\n- The session couldn't be reached.\n\n**Why**\n\nYou can now send work in a remote or cloud-attached session to the background with the same shortcut you use locally. If it does not work, the notice tells you why. When the session simply didn't answer, check before trying again, because the work may have moved anyway.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}