Speed up responses with fast mode
Source: Hacker News
Toggle fast mode
Toggle fast mode in either of these ways:
- Type
/fastand press Tab to toggle on or off. - Set
"fastMode": truein your user settings file.
Fast mode persists across sessions. For the best cost efficiency, enable fast mode at the start of a session rather than switching mid‑conversation. See Understand the cost tradeoff for details.
When you enable fast mode:
- If you’re on a different model, Claude Code automatically switches to Opus 4.6.
- You’ll see a confirmation message: “Fast mode ON”.
- A small
↯icon appears next to the prompt while fast mode is active. - Run
/fastagain at any time to check whether fast mode is on or off.
When you disable fast mode with /fast again, you remain on Opus 4.6. The model does not revert to your previous model. To switch to a different model, use /model.
Understand the cost tradeoff
Fast mode has higher per‑token pricing than standard Opus 4.6:
| Mode | Input (MTok) | Output (MTok) | Price (USD) |
|---|---|---|---|
| Fast mode on Opus 4.6 ( 200 K) | $60 | $225 | — |
Fast mode is compatible with the 1 M token extended context window.
If you switch into fast mode mid‑conversation, you pay the full fast‑mode uncached input‑token price for the entire conversation context, which costs more than enabling fast mode from the start.
Decide when to use fast mode
Fast mode is best for interactive work where response latency matters more than cost:
- Rapid iteration on code changes
- Live debugging sessions
- Time‑sensitive work with tight deadlines
Standard mode is better for:
- Long autonomous tasks where speed matters less
- Batch processing or CI/CD pipelines
- Cost‑sensitive workloads
Fast mode vs effort level
| Setting | Effect |
|---|---|
| Fast mode | Same model quality, lower latency, higher cost |
| Lower effort level | Less thinking time, faster responses, potentially lower quality on complex tasks |
You can combine both: use fast mode with a lower effort level for maximum speed on straightforward tasks.
Requirements
Fast mode requires all of the following:
- Not available on third‑party cloud providers: unavailable on Amazon Bedrock, Google Vertex AI, or Microsoft Azure Foundry. It is available through the Anthropic Console API and for Claude subscription plans using extra usage.
- Extra usage enabled: your account must have extra usage enabled, allowing billing beyond your plan’s included usage. For individual accounts, enable this in your Console billing settings. For Teams and Enterprise, an admin must enable extra usage for the organization.
- Admin enablement for Teams and Enterprise: fast mode is disabled by default for Teams and Enterprise organizations. An admin must explicitly enable it before users can access it.
Enable fast mode for your organization
Admins can enable fast mode in:
- Console (API customers): Claude Code preferences
- Claude AI (Teams and Enterprise): Admin Settings > Claude Code – link
Handle rate limits
Fast mode has separate rate limits from standard Opus 4.6. When you hit the fast‑mode rate limit or run out of extra usage credits:
- Fast mode automatically falls back to standard Opus 4.6.
- The
↯icon turns gray to indicate cooldown. - You continue working at standard speed and pricing.
- When the cooldown expires, fast mode automatically re‑enables.
To disable fast mode manually instead of waiting for cooldown, run /fast again.
Research preview
Fast mode is a research preview feature, meaning:
- The feature may change based on feedback.
- Availability and pricing are subject to change.
- The underlying API configuration may evolve.
Report issues or feedback through your usual Anthropic support channels.
See also
- Model configuration: switch models and adjust effort levels
- Manage costs effectively: track token usage and reduce costs
- Status line configuration: display model and context information