Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
In DevelopmentKind: in v2.1.236,
In DevelopmentSection of the release
The approaching-limit notice is behind tengu_vellum_anchor, which falls back to false.
What
A user-facing message, "Approaching your 5-hour usage limit — Claude will wrap up the current step.", is shown before the existing wrap-up instruction is injected, so the behaviour is explained rather than silent. It is behind the tengu_vellum_anchor flag, which falls back to false, so it is off in this build unless remote config enables it.
Evidence
Approaching your 5-hour usage limit — Claude will wrap up the current step.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Feature flag
tengu_vellum_anchorOff in both readings
The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.236: off
Flag reading movedThe flag server now returns off for tengu_vellum_anchor, read as this account.A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading movedThe flag server now returns nothing at all, having stopped carrying it for tengu_vellum_anchor, read as this account.A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
