tengu_vellum_anchor

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.229, including the newest one read.

Releases whose published page names tengu_vellum_anchor.

1. v2.1.236 19 Aug 2026
   Visible notice when approaching the 5-hour usage limit

   You could be told when you are near the 5-hour usage limit instead of Claude just wrapping up.

   gate cited by this entry, found in this entry's text

2. v2.1.232 13 Aug 2026
   Rate-limit checkpoint can commit in-progress work to a hidden git ref

   Before a usage limit cuts you off, your work can be committed to a hidden git ref with resume notes.

   gate cited by this entry, found in this entry's text

3. v2.1.229 12 Aug 2026
   Rate-limit banner can say "progress saved"

   The out-of-credits message can add a "progress saved" note, off unless a server enables it.

   gate cited by this entry, found in this entry's text

4. v2.1.229 12 Aug 2026
   Usage-limit messages can be told your progress was saved

   Usage-limit messages can append "progress saved", but callers only pass it when a server flag is on.

   gate cited by this entry, found in this entry's text

5. v2.1.229 12 Aug 2026
   Nudge to wrap up when your 5-hour usage is nearly spent

   Claude could be told to wrap up and list remaining work when your usage is nearly spent.

   gate cited by this entry, found in this entry's text

6. v2.1.229 12 Aug 2026
   Rate-limit banner can queue an automatic continue at reset

   Hitting a five-hour limit could queue your turn to resume automatically at reset, currently off.

   gate cited by this entry, found in this entry's text

7. v2.1.229 12 Aug 2026
   Wrap-up hint when you are close to the usage limit

   Past 95% of five-hour usage Claude could be told to checkpoint and list remaining work, off here.

   gate cited by this entry, found in this entry's text

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.

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.

The earliest release whose published evidence quoted tengu_vellum_anchor was v2.1.229, 12 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

One 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.