tengu_ochre_kite
A Claude Code feature flag, read out of the shipped bundle. It was in the build from v2.1.273 and was gone by v2.1.282.
Claude Code now recovers gracefully when a safety filter cuts off a response mid-tool-call
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.273.
In the changelogs
3Releases whose published page names tengu_ochre_kite.
-
v2.1.282
One retry after a safety stop is now on for everyone, with a way to opt out
When safeguards stop a response, Claude Code now retries once on the same model by default; set
CLAUDE_CODE_DISABLE_REFUSAL_RETRYto turn this offgate cited by this entry
-
v2.1.282
Retry after a safety-classifier refusal is now on for everyone, with a way to turn it off
Refusal retry no longer needs a server flag or an opt-in variable, and
CLAUDE_CODE_DISABLE_REFUSAL_RETRYnow turns it offgate cited by this entry
-
v2.1.273
New safety-classifier refusal recovery path (tengu_ochre_kite)
Claude Code now recovers gracefully when a safety filter cuts off a response mid-tool-call
gate cited by this entry, found in this entry's text
Gate readings
2| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.282 read on another version | Off in both readings | off | off | not a boolean we can read |
| v2.1.273 read on another version | Not enough to say | no value returned | no value returned | off |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
Flag server, over time
4| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | off | 2026-10-17T05:30:04Z | 2026-11-12T05:55:04Z | v2.1.302 to v2.1.322 |
| this account | off | 2026-09-15T21:20:04Z | 2026-11-12T05:55:04Z | v2.1.273 to v2.1.322 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | off | 2026-09-15T21:10:05Z | 2026-10-17T05:10:04Z | v2.1.273 to v2.1.302 |
One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.
First cited
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Presence across releases
2Build by build
45One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.