What it is
OAuth token refresh lock now reports its "acquired" event later, closer to the actual read check
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.265.
Presence across releases
0The 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.
First cited
1The earliest release whose published evidence quoted tengu_oauth_token_refresh_lock_acquired was v2.1.265, 8 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 above.
Gate readings
0No 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.
Names beside it
Every feature flag in the inventory starting tengu_oauth_token_refresh_lock, up to twelve of them.
tengu_oauth_token_refresh_lock_acquiringOAuth token refresh lock now reports its "acquired" event later, closer to the actual read check never mined
tengu_oauth_token_refresh_lock_release_errorA telemetry failure can no longer block releasing the OAuth token refresh lock never mined
tengu_oauth_token_refresh_lock_releasingA telemetry failure can no longer block releasing the OAuth token refresh lock never mined
tengu_oauth_token_refresh_locked_read_failedLogin token refresh retries saving and stops cleanly on dead tokens instead of failing quietly. 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.