Beside the lead

A tool-schema change in Claude Code broke it on non-Anthropic backends for two days

Claude Code 2.1.268 fixed a fault that had failed every turn sent through a third-party endpoint since 8 September. The release notes, published at 20:30 UTC on 10 September, trace it to “a regex in the Artifact tool’s input schema that those endpoints reject,” first shipped in 2.1.265 at 20:37 UTC on 8 September. Two more releases went out with the fault, and every affected turn returned HTTP 400.

DeepSeek’s documentation names exactly this route, taking Anthropic-format requests at api.deepseek.com/anthropic and listing Claude Code as a client. The notes name no endpoint, but the class is plain: a change to a tool definition, not to any model, stopped the harness working through any gateway that rejects that regex.

The same release stops plain WebFetch deny and ask rules from applying to Artifact tool reads and updates, so a settings file that gated fetching broadly now needs an Artifact rule to keep the same cover.

What it changes If you run Claude Code against any non-Anthropic endpoint, update to 2.1.268. If your settings deny or gate WebFetch broadly, add an Artifact rule, because the WebFetch rule no longer covers it.

Primary source read

Who is telling you this

Anthropic on GitHub · primary

Written by
Release published by the GitHub account ashwin-ant
For
Anthropic
What they gain if this is true
The paper’s best guess: a vendor whose harness is also a way to use rival backends has little commercial reason to hurry a fix for those backends, and this one still shipped within two days.

Published in the edition of Friday, 11 September 2026 · Beat: Tooling