{"version":"2.1.301","anchor":"background-bash-calls-classified-as-foreground-kept-or-und","canonical_anchor":"background-bash-calls-classified-as-foreground-kept-or-und","heading":"Claude Code now sorts background shell commands into kinds","tier":"internal","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/background-bash-calls-classified-as-foreground-kept-or-und","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Claude Code now sorts background shell commands into kinds\n\nClaude Code now labels each shell command as running in the foreground, kept in the background, or under a permission rule\n\n**Unclear.** What Claude Code does with these labels, and whether it is switched on, is not clear.\n\n**What**\n\nClaude Code runs shell commands through its Bash tool, and a command can be set to run in the background, meaning it keeps going while Claude does other work. Claude Code now labels each such command:\n\n- foreground: the command is not set to run in the background\n\n- under_a_rule: it runs in the background and one of your deny or ask permission rules matches it\n\n- kept: it runs in the background and no such rule matches\n\n**Why**\n\nThis can affect whether background commands keep running and how they are reported.\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"}