{"version":"2.1.281","anchor":"headless-unavailable-in-this-environment-slash-command-rep","canonical_anchor":"headless-unavailable-in-this-environment-slash-command-rep","heading":"Headless 'unavailable in this environment' slash-command reply is tagged with commandOutcome","tier":"notice","area":"SDK","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/headless-unavailable-in-this-environment-slash-command-rep","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Headless 'unavailable in this environment' slash-command reply is tagged with commandOutcome\n\nNon-interactive runs now tag the reply to an unavailable slash command with `commandOutcome` of `unavailable_headless`\n\n**What**\n\nA non-interactive run is one without the interactive screen, such as a script. When such a run uses a slash command that is not available there, the message written to its output now includes `commandOutcome: { kind: \"unavailable_headless\" }`. Slash commands are commands typed with a leading `\/`. `commandOutcome` is a new field, and its other kinds include:\n\n- `unknown`\n\n- `failed`\n\n- `restart_required`\n\n**Why**\n\nScripts and programs reading Claude Code's output can check this field to see why a command did not run, instead of parsing the message text.\n\n- Area: SDK\n- Names: `commandOutcome`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}