The wire · review · first seen Nov 10, 10:32 UTC

Anthropic adds Claude Code fast mode on Vertex

Claude Code v2.1.322 shipped fast mode on Vertex in the global, us and eu regions. For a builder using Vertex, the practical question is whether fast mode fits a workflow that may fall back to standard speed.

L0 · primary1 source2 claims checked4 min read

What shipped

The v2.1.322 release notes say Claude Code added fast mode on Vertex in the global, us and eu regions. This is a shipped change, not a scheduled feature. The regional list matters: the note names those three regions, but does not establish availability elsewhere. A team already using Vertex can assess the change against its own region rather than treating “on Vertex” as a blanket availability statement. [1]

The same release note says Claude Code falls back to standard speed if Vertex refuses fast mode. That is the stated behavior for a refusal; the note does not say that every request will use fast mode. When evaluating a session, keep the requested mode separate from the speed actually used. Otherwise, a completed task could be mistaken for evidence that Vertex accepted fast mode. [1]

These are two parts of one release-note entry: a fast-mode addition in named Vertex regions and a fallback when Vertex refuses it. The entry does not describe a new command, configuration option or indicator for the fallback. Treat v2.1.322 as the version to examine, but do not infer an activation procedure from the short note. The defensible conclusion is that the behavior shipped, not that every operational detail is documented here. [1][2]

Why it matters if you build

If Claude Code is already part of a Vertex-based workflow in one of the named regions, this release gives you a concrete behavior to test today. Run work that represents your usual use, then check whether fast mode was accepted or standard speed was used. The fallback makes a refusal relevant to the evaluation rather than simply a failed attempt to use fast mode. The source does not say how often refusals occur. [1][2]

Do not make a cost decision from this release note alone. It provides no prices, billing rules or comparison between fast and standard speed. Nor does it give a measured latency difference. “Fast mode” is the feature name in the artifact, not a quantified performance result. A builder deciding whether to change routine usage needs those missing details or observations from the actual workflow before treating this as a cost or performance improvement. [1][2]

The regional scope is a practical limit. A workflow on Vertex in global, us or eu falls within the regions named by the release note; one outside them is not covered by this claim. Even within that scope, fallback means acceptance cannot be assumed from availability alone. For a decision made today, separate three questions: whether your region is named, whether Vertex accepts fast mode for your use, and whether the observed behavior is worth adopting. [1][2]

How to try it today

1. Check whether the Claude Code version you are evaluating is v2.1.322.
2. Check whether your Vertex use is in global, us or eu.
3. Attempt a representative Claude Code task with Vertex fast mode. Do not assume the release note specifies how to enable it.
4. Check whether Vertex accepted fast mode or Claude Code fell back to standard speed.
5. Decide based on the behavior you can verify in your workflow, not on an assumed speed or cost benefit.

What we checked

Every claim below was walked down the source ladder. The rung is how close the source is to the thing itself; the tense is the source's own.

1. shipped L0 · primary

   Claude Code v2.1.322 adds fast mode on Vertex in the global, us and eu regions.

   per GitHub releases · anthropics/claude-code (L0)
2. shipped L0 · primary

   Claude Code falls back to standard speed if Vertex refuses fast mode.

   per GitHub releases · anthropics/claude-code (L0)

What is not confirmed

The supplied release note does not establish the price of fast mode, the billing effect of fallback, a speed difference, or a performance guarantee. It also gives no rate, condition or explanation for Vertex refusing fast mode. Those omissions matter if the decision depends on a predictable budget or on consistently getting fast mode. [1][2]

The note does not establish support outside global, us and eu. It does not give an activation command, an interface path, a way to identify fallback, or instructions for diagnosing a refusal. Do not turn those gaps into assumed product behavior; confirm them before writing a team procedure. [1][2]

Who should act, who should wait

Move now if you already use Claude Code with Vertex in a named region and can test the behavior in your own workflow. The shipped change gives you something specific to evaluate, and the stated fallback gives you a reason to check what actually happened. A limited trial is more justified by this evidence than a blanket change to team practice. [1][2]

Wait on a broader rollout if you need a confirmed cost, a measured speed benefit, guaranteed fast-mode acceptance, or support in another region. None of those is established by this entry. The release note supports trying the shipped behavior in its named scope; it does not support a claim that the result will be faster or cheaper for your work. [1][2]

Sources

• v2.1.322 — GitHub releases · anthropics/claude-code L0 · primary