{"version":"2.1.309","anchor":"failed-background-command-keeps-stdout-and-stderr","canonical_anchor":"failed-background-command-keeps-stdout-and-stderr","heading":"Failed background commands now show both their output and their error messages","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/failed-background-command-keeps-stdout-and-stderr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Failed background commands now show both their output and their error messages\n\nWhen a background command fails, Claude Code now reads its saved output and shows it together with any error messages\n\n**What**\n\nA background command keeps running while you and Claude carry on. Some send their normal output (stdout) to a file. Before, if such a command failed, Claude Code read that file only when the command printed no error messages (stderr).\n\nNow, when the command fails, Claude Code always reads the file. If there are error messages too, it combines the two.\n\n**Why**\n\nWhen a background command fails, you and Claude see what it printed as well as what went wrong, instead of only the error messages.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}