{"version":"2.1.281","anchor":"unknown-slash-command-in-non-interactive-mode-records-a-stru","canonical_anchor":"unknown-slash-command-in-non-interactive-mode-records-a-stru","heading":"Unknown slash command in non-interactive mode records a structured outcome","tier":"notice","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/unknown-slash-command-in-non-interactive-mode-records-a-stru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Unknown slash command in non-interactive mode records a structured outcome\n\nIn non-interactive runs, the 'Unknown command' reply now carries a structured record of the outcome and the suggested command\n\n**Unclear.** The finding does not say where this outcome record can be read.\n\n**What**\n\nA non-interactive session is a run with no screen to type into, such as a scripted run. When you use a slash command that does not exist in one, Claude Code replies \"Unknown command: \/x. Did you mean \/y?\". That reply is now built as a user message and carries `commandOutcome: { kind: \"unknown\", suggestion }`, which records the unknown command and the suggestion.\n\n**Why**\n\nThe outcome of a mistyped command is now recorded in a structured form instead of existing only as text.\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}