Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Home / Reference / Feature flags

tengu_oauth_refresh_token_account_on_hold

flag never mined JSON

A Claude Code feature flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

OAuth token refresh now recognizes an 'account on hold' response as its own outcome

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

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 149on this box, as of v2.1.308
Written about v2.1.235 first named in a changelog, 18 Aug 2026

In the changelogs

3

Releases whose published page names tengu_oauth_refresh_token_account_on_hold.

  1. v2.1.269
    OAuth refresh now tracks whether the plugins scope was requested/granted, with automatic downgrade retry on invalid_scope

    OAuth token refresh now requests a plugins scope and retries without it if the server rejects the scope

    gate cited by this entry

  2. v2.1.235
    OAuth refresh recognises an 'account on hold' response

    OAuth token refresh now recognizes an 'account on hold' response as its own outcome

    gate cited by this entry

  3. v2.1.235
    Account-on-hold handling is built end-to-end but dark behind tengu_lively_beaver (fallback: off)

    A full account-on-hold sign-in flow was added but stays unreachable pending a server-side gate

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

Gate readings

0

No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.

First cited

1

The earliest release whose published evidence quoted tengu_oauth_refresh_token_account_on_hold was v2.1.235, 18 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.

ReleaseDateThe span that was quoted
v2.1.23518 Aug 2026tengu_oauth_refresh_token_account_on_hold

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

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