Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

tengu_tidy_lemon

flag in the build JSON

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

A remotely controlled option lets team members send a more-usage request to their admin directly from /rate-limit-options

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.283.

First seen v2.1.283 25 Sep 2026
Last seen v2.1.283 25 Sep 2026
Builds1 / 126on this box, as of v2.1.283
Written about v2.1.283 first named in a changelog, 25 Sep 2026
v2.1.283in the build not in the build never minedv2.1.283

In the changelogs

3

Releases whose published page names tengu_tidy_lemon.

  1. v2.1.283
    Asking an admin for more usage can happen in one step from the limit menu

    A remotely controlled option lets team members send a more-usage request to their admin directly from /rate-limit-options

    gate cited by this entry

  2. v2.1.283
    Remote setting for how you ask an admin for more usage

    A remote setting can let the rate-limit menu send an admin usage request in one step, or show custom wording in the confirmation dialog

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

  3. v2.1.283
    Wording of the admin usage-credit request dialog can now be changed remotely

    The dialog for asking your admin for usage credits can now take its title, text and button labels from a remotely set value

    gate cited by this entry

Gate readings

1
ReleaseResolvedThis accountAnonymousCompiled default
v2.1.283 read on another version Not enough to say no value returned no value returned not a boolean we can read

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.

First cited

2

The earliest release whose published evidence quoted tengu_tidy_lemon was v2.1.283, 25 Sep 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.

ReleaseDateThe span that was quoted
v2.1.28325 Sep 2026let i = x("tengu_tidy_lemon", null);
v2.1.28325 Sep 2026tengu_tidy_lemon

Presence across releases

1
BuildsHow manyDatesReading
v2.1.2831 build25 Sep 2026 ◆in the build

Build by build

1

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.

BuildDateStateThe record behind it
v2.1.28325 Sep 2026·addedverdict: added · default null

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.

Feedback