Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

commandOutcome

setting never mined JSON

A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

SDK results for local slash commands now include a commandOutcome saying whether the command failed or was unavailable

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.281.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 126on this box, as of v2.1.283
Written about v2.1.281 first named in a changelog, 23 Sep 2026

In the changelogs

5

Releases whose published page names commandOutcome.

  1. v2.1.281
    SDK local-command messages now carry a commandOutcome (failed / unavailable_headless / ...)

    SDK results for local slash commands now include a commandOutcome saying whether the command failed or was unavailable

    found in this entry's text

  2. v2.1.281
    Unknown slash command in non-interactive mode records a structured outcome

    In non-interactive runs, the 'Unknown command' reply now carries a structured record of the outcome and the suggested command

    found in this entry's text

  3. v2.1.281
    Headless 'unavailable in this environment' slash-command reply is tagged with commandOutcome

    Non-interactive runs now tag the reply to an unavailable slash command with commandOutcome of unavailable_headless

    named in this entry, found in this entry's text

  4. v2.1.281
    Slash command results now record a failure outcome

    Slash commands now record whether they failed, with the skill usage command and /recap marking their errors as failed

    found in this entry's text

  5. v2.1.281
    Minor internals: link sanitizer, local command outcome, create-repo UI, hooks worker state

    Small internal changes: a link sanitizer that writes "(link removed)", command outcomes on messages, a simpler repo-name dialog

    found in this entry's text

First cited

3

The earliest release whose published evidence quoted commandOutcome was v2.1.281, 23 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.28123 Sep 2026commandOutcome:
v2.1.28123 Sep 2026commandOutcome: { kind: "failed" }
v2.1.28123 Sep 2026commandOutcome: { kind: "unavailable_headless" }

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback