{"version":"2.1.319","anchor":"retry-gate-tengu-woolly-kettle-for-500-responses-marked-x-sh","canonical_anchor":"retry-gate-tengu-woolly-kettle-for-500-responses-marked-x-sh","heading":"Claude Code can now detect server errors that say not to retry","tier":"soon","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/retry-gate-tengu-woolly-kettle-for-500-responses-marked-x-sh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Claude Code can now detect server errors that say not to retry\n\nClaude Code can now pick out server errors marked `x-should-retry: false`, behind a setting that is off by default\n\n**Unclear.** What Claude Code does differently when it recognises one of these errors.\n\n**What**\n\nClaude Code can now recognise a server error (status 500) that comes with the header `x-should-retry: false`, which is the server saying the request should not be tried again. This only works when the `tengu_woolly_kettle` setting is on, and it is off unless switched on remotely. Earlier readings of that setting returned off for this site's account and for a signed-out account.\n\n**Why**\n\nThis may change what Claude Code does after such an error, for example whether it tries the request again.\n\n- Flag `tengu_woolly_kettle`: Off in both readings (read for one account on one subscription tier against v2.1.319; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}