{"version":"2.1.280","anchor":"killed-shell-commands-can-now-be-flagged-as-having-no-real-e","canonical_anchor":"killed-shell-commands-can-now-be-flagged-as-having-no-real-e","heading":"Killed shell commands can now be flagged as having no real exit status","tier":"internal","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/killed-shell-commands-can-now-be-flagged-as-having-no-real-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Killed shell commands can now be flagged as having no real exit status\n\nForce-killed shell commands are now flagged as having no real exit status\n\n**What**\n\nWhen a shell command has to be force-killed via a fallback escalation (sending `SIGKILL` after a normal stop attempt fails), its result now carries a `noExitStatus` field marking that the reported exit code isn't a genuine one reported by the process, but an inferred stand-in.\n\n**Why**\n\nThis lets anything reading the result tell apart a command that actually reported its own exit code from one that was forcibly terminated, avoiding misleading conclusions drawn from a fake exit status.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}