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

Claude Code v2.1.307 ·

Members who hit their spend limit can ask an admin for more from the VS Code limit banner

A new adminRequestOffer lets Team/Enterprise members hitting their own spend limit send a 'Request more' ask to their admin from VS Code

Group of 2 You'll notice Notable New Features
JSON All of v2.1.307
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
VS CodeArea: what it touches
New FeaturesKind: in v2.1.307,
What probably matters to youSection of the release

What

There is a new flow for Team and Enterprise members who reach their own spend limit (the most usage their organisation lets them have). In the VS Code extension, the banner that appears when you hit a limit can now offer a button to ask your admin for a higher limit.

  • adminRequestOffer is a new optional part of the usage and limit information. It moves through the states can_ask, pending, sending and sent, and carries its own wording: a button label, a label shown once the request is done, and a confirmation message.
  • The default wording is 'Request more' and 'Request sent to your admin ✓'.
  • admin_limit_request is a new request method, which is the call that sends the ask to the admin.
  • The offer depends on two remotely controlled switches, tengu_tallow_quoit_gate (default false) and tengu_tallow_quoit (a settings object that includes a vscode block for the wording). Related names tengu_tallow_quoit_wall and tengu_tallow_quoit_filed also appear. Nothing has been read about whether any of them is turned on.

Why

If you are capped by your organisation, this gives you a way to ask for more usage from where you hit the limit instead of contacting your admin separately. As described here it appears in the VS Code extension only, and whether you see it depends on remote switches.

Read from
Feature flag
tengu_tallow_quoit Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.307: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.307. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns null for tengu_tallow_quoit, 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 moved The flag server now returns nothing at all, having stopped carrying it for tengu_tallow_quoit, 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.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_tallow_quoit

See this entry in the whole of v2.1.307 →

Feedback