{"version":"2.1.304","anchor":"api-error-retry-rule-for-unsupported-context-management","canonical_anchor":"api-error-retry-rule-for-unsupported-context-management","heading":"Claude Code recognises servers that reject the context_management field","tier":"notice","area":"API","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/api-error-retry-rule-for-unsupported-context-management","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Claude Code recognises servers that reject the context_management field\n\nClaude Code now recognises the error a server returns when it refuses the context_management field in a request\n\n**Unclear.** What Claude Code does after recognising this error, such as retrying without the field, is not stated.\n\n**What**\n\nWith some requests, Claude Code sends a field called `context_management`, which tells the API how to handle earlier conversation. Some servers between you and the API, such as a company proxy or gateway, do not accept this field. They reply with the error \"context_management: Extra inputs are not permitted\".\n\nClaude Code now has a rule that recognises this error. It sits next to an existing rule for a similar error about the `evict_on_complete` option.\n\n**Why**\n\nIf you connect through a proxy or gateway that does not support newer request fields, Claude Code can now identify this error and react to it, instead of treating it as an unknown failure.\n\n- Area: API\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}