{"version":"2.1.281","anchor":"new-local-command-outcome-field-on-local-command-transcript","canonical_anchor":"new-local-command-outcome-field-on-local-command-transcript","heading":"New local_command_outcome field on local-command transcript rows","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-local-command-outcome-field-on-local-command-transcript","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New local_command_outcome field on local-command transcript rows\n\nSDK transcripts can now mark why a local command failed, with kinds such as unknown command or restart required\n\n**What**\n\nThe SDK message format (how Claude Code describes a conversation to a program driving it) gains an internal `local_command_outcome` field on rows recording local commands. Its kinds are:\n\n- `unavailable_headless`\n\n- `unknown`, with a suggestion of the closest command\n\n- `failed`\n\n- `restart_required`\n\n**Why**\n\nA program showing the conversation can offer a fix, such as a corrected command name, instead of just passing the error text along."}