{"version":"2.1.280","anchor":"structured-error-objects-with-a-codedescription-now-get-a-d","canonical_anchor":"structured-error-objects-with-a-codedescription-now-get-a-d","heading":"Structured error objects with a code+description now get a dedicated short summary","tier":"notice","area":"Error Handling","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/structured-error-objects-with-a-codedescription-now-get-a-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Structured error objects with a code+description now get a dedicated short summary\n\nError messages with a code and description now show a short, dedicated summary instead of a scanned-out file path or command\n\n**What**\n\nClaude Code shows short summaries for errors in places like tool call results. There is internal logic that picks what text to use for that summary. Now, when an error is a structured object containing both a `code` field and a non-empty `description` field, the summary is built directly from that `description` (cleaned up and cut off at 60 characters). Previously such errors would instead be handled by logic that scans for fields like `command`, `file_path`, or `path` to build a summary.\n\n**Why**\n\nThis means errors that carry a proper `code` and `description` now get a summary that reflects the actual error description, rather than one accidentally built from an unrelated field like a file path or command string.\n\n- Area: Error Handling\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}