{"version":"2.1.281","anchor":"output-configeffort-400-errors-on-a-message-now-go-to-the-o","canonical_anchor":"output-configeffort-400-errors-on-a-message-now-go-to-the-o","heading":"output_config.effort 400 errors on a message now go to the output_config fallback path","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/output-configeffort-400-errors-on-a-message-now-go-to-the-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### output_config.effort 400 errors on a message now go to the output_config fallback path\n\nAn API 400 error naming a message's output_config.effort is now treated as an unsupported-effort error and falls back\n\n**What**\n\nClaude Code sorts API errors that mention `output_config`, which carries the effort option. A 400 error is the API rejecting a request as invalid. Before, any 400 error saying effort is not supported when thinking is disabled was left alone.\n\nNow that error is left alone only if it does not also point at a specific message's effort, in the form `messages.N: output_config.effort`. An error that does point there is treated as \"effort unsupported\", and the usual fallback of sending the request without effort applies.\n\n**Why**\n\nRequests the API rejected because of effort on a specific message can now recover through the fallback instead of failing."}