{"version":"2.1.315","anchor":"background-bash-tasks-carry-a-backgroundtrigger-and-run-an-e","canonical_anchor":"background-bash-tasks-carry-a-backgroundtrigger-and-run-an-e","heading":"Backgrounded shell commands now record what sent them there and run an exit step","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/background-bash-tasks-carry-a-backgroundtrigger-and-run-an-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Backgrounded shell commands now record what sent them there and run an exit step\n\nWhen a shell command is moved to the background, Claude Code now records what triggered the move and attaches a step that runs at exit\n\n**Unclear.** What the new exit step does to a backgrounded command is not stated.\n\n**What**\n\nClaude Code can move a shell command (a command it runs in your terminal) into the background so it keeps running while other work goes on. When it does this, it now records what triggered the move to the background. It also attaches a handler that runs when the command exits, and passes the command's text along when the task finishes.\n\nPreviously the command was sent to the background with no extra options.\n\n**Why**\n\nThis changes what happens to background shell tasks when they end.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}