{"version":"2.1.301","anchor":"background-task-output-may-live-on-another-machine","canonical_anchor":"background-task-output-may-live-on-another-machine","heading":"Background command output can now be recorded as stored elsewhere","tier":"internal","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/background-task-output-may-live-on-another-machine","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Background command output can now be recorded as stored elsewhere\n\nClaude Code can now note when a background command's output file is on a different machine from the one it runs on\n\n**What**\n\nThe Bash tool runs shell commands, and some of them run in the background. The internal information Claude Code keeps about a background command can now record where its output is saved. It can also mark that the output file is not on the machine Claude Code itself is running on.\n\n**Why**\n\nThis suggests commands may be run on a remote or hosted machine.\n\n- Area: Background Shells\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}