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
HomeDocsClaude Developer Platform 21 Oct 2026
One change · api

fast-mode changedbuild-with-claude/fast-mode

Nearest release: v2.1.307, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+3added
Lines−3removed
From line 181 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits17to this page, all time

The whole hunk

from line 181, old and new numbered
/
lines
from line 181
181181 client = Anthropic::Client.new
182182 
183183 response = client.messages.create(
184 model: "claude-opus-5-5",
184 model: Anthropic::Model::CLAUDE_OPUS_5_5,
185185 max_tokens: 4096,
186186 speed: "fast",
187187 messages: [{role: "user", content: "Refactor this module to use dependency injection"}]
from line 363
363363 client = Anthropic::Client.new
364364 
365365 response = client.messages.create(
366 model: "claude-opus-5-5",
366 model: Anthropic::Model::CLAUDE_OPUS_5_5,
367367 max_tokens: 1024,
368368 speed: "fast",
369369 messages: [{ role: "user", content: "Hello" }]
from line 400
400400If you'd prefer to fall back to standard speed rather than wait for fast mode capacity, catch the rate limit error and retry without `speed: "fast"`. Set `max_retries` (typescript, java, php: `maxRetries`; csharp: `MaxRetries`; go: `option.WithMaxRetries`) to `0` on the initial fast request to skip automatic retries and fail immediately on rate limit errors.
401401 
402402<Note>
403 Falling back from fast to standard speed will result in a [prompt cache](https://platform.claude.com/docs/en/build-with-claude/prompt-caching) miss. Requests at different speeds do not share cached prefixes.
403 Falling back from fast to standard speed results in a [prompt cache](https://platform.claude.com/docs/en/build-with-claude/prompt-caching) miss. Requests at different speeds do not share cached prefixes.
404404</Note>
405405 
406406Because setting `max_retries` (typescript, java, php: `maxRetries`; csharp: `MaxRetries`; go: `option.WithMaxRetries`) to `0` also disables retries for other transient errors (overloaded, internal server errors), the following examples reissue the original request with default retries for those cases.
Feedback