{"version":"2.1.309","anchor":"remote-background-task-note-no-longer-references-a-task-chec","canonical_anchor":"remote-background-task-note-no-longer-references-a-task-chec","heading":"Note about remote background commands no longer points to a status check","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/remote-background-task-note-no-longer-references-a-task-chec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Note about remote background commands no longer points to a status check\n\nClaude is now always told that a remote background command's output file shows what it printed, not whether it is still running\n\n**What**\n\nWhen Claude starts a command in the background in a remote session, it gets a note about it. The note now always says that the command's output file shows what it has printed, not whether it is still running. In earlier builds the note could instead tell Claude to check on the command by calling a status tool with the command's ID. That version has been removed.\n\n**Why**\n\nThis is a small change to what Claude is told. It may affect how Claude checks on background commands in remote sessions.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}