Omniscio

OmniscioGuidesExtra inputs are not permitted

Claude Code: Extra inputs are not permitted (400)

Last checked against Anthropic's documentation on November 18, 2026. By the Omniscio team. Updated .

What is the exact message?

API Error: 400 ... context_management: Extra inputs are not permitted

The text before the colon varies: it can name defer_loading, tool_reference or diagnostics. The field name is the part that tells you which fix applies.

What does it mean?

The endpoint that received the request rejected one of its fields as an input it does not accept. The endpoint's own message names that field, which is why the line carries it.

Claude Code sends beta-only fields such as context_management and tool search's defer_loading alongside an anthropic-beta header that enables them. Both parts have to arrive together.

What causes it

  • A gateway dropped the header. It forwards the body but not anthropic-beta, so the API sees fields it has no permission to accept.
  • The upstream uses another schema. A gateway forwarding an Anthropic-format body upstream gets those fields rejected by a provider that does not define them.
  • Nothing changed on your side. Usually that is the case: the request carries these beta fields, and a gateway that forwards the body but strips the header has them rejected.
  • The session moved provider without a restart. Before v2.1.302 the error could name diagnostics with no gateway involved, when a session that had already used the Anthropic API moved to Amazon Bedrock or Google Cloud's Agent Platform.

How do I fix it?

  1. Update Claude Code first. Run claude update. From v2.1.304 it answers a context_management rejection by sending the request once more without the field; from v2.1.305 it does the same for defer_loading and tool_reference. That clears the error for you, though the beta features those fields carry stay off.
  2. Fix the gateway if you control it. Configure it to forward the anthropic-beta header with the body, and check that its upstream accepts the fields that header enables. That is the only step that keeps the beta features on.
  3. Turn the beta fields off as a fallback. Set CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS=1 before launching Claude Code. The pre-release capabilities go and the request stops carrying them.
  4. If the field is diagnostics, the session switched provider mid-life, for example to Bedrock. On a build before v2.1.302, run /clear or start a new session; v2.1.302 and later handle the switch without the error.

How do I know it is fixed?

  • The next request gets an answer instead of the 400.
  • The line stops naming a field after the update, even with the same gateway in the path.
  • With CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS=1 set, the request goes through, which is consistent with the beta fields being the cause.

Where these answers come from

  • The message, quoted word for word, the beta header pairing, the version numbers and the diagnostics note: Anthropic's error reference, read November 18, 2026.
  • What a gateway must forward, the retry without tool search fields, and the full scope of the switch: LLM gateway protocol, read November 18, 2026.
  • CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS: Environment variables, read November 18, 2026.

Common questions

What is the field the message names?

It is the request field the endpoint refused, such as context_management or defer_loading. Claude Code sends those beta fields with the header that enables them.

Why does a gateway cause this?

It forwards the body without the anthropic-beta header, so the API receives fields it has not been told to accept. A gateway whose upstream uses another schema rejects them too.

Does updating Claude Code fix it?

It often does. v2.1.304 and later retry without context_management, and v2.1.305 and later retry without the tool search fields. Older versions did not retry at all.

Do I lose anything by turning the beta fields off?

You lose the pre-release capabilities those fields carry, and nothing else. Anthropic lists the full scope: context management, beta tool schema fields, structured output, and MCP tool search, so every MCP tool loads upfront. An update to v2.1.304 or later carries the same loss, because Claude Code then retries without the field.