{"version":"2.1.290","anchor":"background-command-message-no-longer-points-to-the-output-fi","canonical_anchor":"background-command-message-no-longer-points-to-the-output-fi","heading":"Claude no longer reads a command's output file to tell if it finished","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/background-command-message-no-longer-points-to-the-output-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Claude no longer reads a command's output file to tell if it finished\n\nFor background commands on a remote host, Claude is now told the host reports whether a command is still running, not its output file\n\n**What**\n\nClaude can run a command in the background on a remote host, writing its output to a file. The message Claude gets back used to say the command was over once the file's last line read `[exited with code N]` or a stopped notice. That instruction is gone. The message now says the host itself reports whether the command is still running, not the file.\n\n**Why**\n\nThis changes how Claude judges whether a background command has finished, so it relies on the host rather than on what the output file happens to end with.\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"}