Claude Code /fast: Same Opus, 2x Speed — Worth It?
Table of Contents
- What is /fast
- A Common Misconception
- How to Use It
- Enable Fast Mode
- Disable Fast Mode
- Check Current Status
- Fast Mode vs Normal Mode
- When to Turn It On
- When to Turn It Off
- Practical Tips
- Tip 1: Default Off, Enable on Demand
- Tip 2: Combine with /model
- Tip 3: Toggle by Development Phase
- Tip 4: Use /cost to Compare Spend
- /fast vs /model vs —model
- Final Thoughts
What is /fast
When using Claude Code, you might run into situations like these:
- A simple change takes over ten seconds to finish, and it feels slow
- You want to iterate quickly on a few approaches, but waiting for each output is frustrating
- The task isn’t complex — you don’t need deep thinking, you just want it done faster
You might wonder: can I speed up the current model without switching to a weaker one?
That’s exactly what the /fast command is for.
/fast is a slash command in Claude Code that toggles “fast mode.” It doesn’t switch to a different model — it makes the current model output faster.
A Common Misconception
Many people assume /fast downgrades your model — switching from Opus to Sonnet, or from Sonnet to Haiku. That’s not what happens.
Fast mode uses the same model. It optimizes output speed at the model level, not by swapping in a weaker model. If you’re on Opus, you stay on Opus — just with faster output.
How to Use It
Enable Fast Mode
In Claude Code’s interactive mode, type:
/fast
You’ll see a confirmation that fast mode is now enabled.
Disable Fast Mode
Type /fast again to turn it off:
/fast
It’s a simple toggle — type it once to enable, type it again to disable.
Check Current Status
Claude Code’s status bar shows whether fast mode is active. You can also type /fast again to confirm the current state.
Fast Mode vs Normal Mode
| Fast Mode | Normal Mode | |
|---|---|---|
| Model | Unchanged, same model | Current model |
| Output Speed | Faster | Standard |
| Thinking Depth | May trade off slightly | Full reasoning |
| Best For | Simple tasks, rapid iteration | Complex tasks, deep reasoning |
| Toggle | /fast to switch | Default state |
The core difference: faster output, but potentially less thorough on complex reasoning.
When to Turn It On
Fast mode shines in these scenarios:
- Simple code changes — renaming a variable, tweaking styles, adding a field — no deep thinking needed
- Rapid iteration — trying multiple approaches back-to-back, and waiting each time is annoying
- Boilerplate generation — writing config files, creating templates, repetitive work
- Q&A and lookups — asking how an API works, checking syntax, understanding a code snippet
- Formatting and cleanup — reorganizing code structure, adding comments, adjusting formatting
When to Turn It Off
For these scenarios, switch back to normal mode:
- Complex architecture design — requires deep reasoning and holistic thinking
- Tricky bug investigation — debugging across multiple files with complex call chains
- Large-scale refactoring — code changes that need careful impact analysis
- Code review — when you need Claude Code to thoroughly read and analyze code quality
The rule of thumb: simple task → on, complex task → off.
Practical Tips
Tip 1: Default Off, Enable on Demand
Keep normal mode as your default and toggle fast mode on when you hit simple tasks or need rapid iteration. This ensures complex tasks always get full reasoning depth.
Tip 2: Combine with /model
/fast and /model work well together. For example:
- Opus + fast mode — the most powerful model at faster speed, great for medium-complexity tasks where you don’t want to wait
- Sonnet + fast mode — everyday development on turbo, simple tasks fly by
- Haiku + normal mode — Haiku is already fast, so fast mode usually isn’t necessary
Tip 3: Toggle by Development Phase
In a typical development workflow, you can use it like this:
- Design phase → Normal mode, let Claude Code think thoroughly
- Coding phase → Enable fast mode, generate code quickly
- Debugging phase → Disable fast mode, analyze problems carefully
- Wrap-up phase → Enable fast mode, handle formatting, comments, etc.
Tip 4: Use /cost to Compare Spend
Fast mode may affect token usage. Use /cost before and after toggling to see the difference, and find the rhythm that works best for you.
/fast vs /model vs —model
| /fast | /model | —model | |
|---|---|---|---|
| Purpose | Toggle fast/normal mode | Switch models | Set model at launch |
| Changes model? | No | Yes | Yes |
| Changes speed? | Yes | Indirectly (different models have different speeds) | Indirectly |
| How to use | Toggle switch | Selection list | CLI argument |
| Persistence | Current session | Current session | Current session |
Each serves a different role: /fast adjusts speed, /model swaps models, --model sets the default. Mix and match freely.
Final Thoughts
/fast is a small command that makes a noticeable difference. The problem it solves is straightforward: you don’t want to change models, you just want faster output.
Not every task needs the model to deliberate at length. For simple tasks, toggling fast mode on makes the experience noticeably smoother.
Next time you’re in Claude Code working on something simple, try typing /fast and feel the speed boost. If it’s not what you need, just /fast again to switch back — after all, it’s just a toggle.
Related Articles
Claude Code Agent Loop: Dissecting the Heart of an AI Coding Assistant
How does Claude Code understand your requests, invoke tools, and self-recover step by step? A source-code deep dive into the Agent Loop's core architecture — streaming responses, parallel tool execution, auto-compaction, and error recovery.
Claude Code settings.json Explained (1): Where Config Files Live and Who Wins
A complete guide to Claude Code's configuration file system — five config sources, their file paths, priority rules, array merging vs value overriding, and enterprise managed settings delivery.
Claude Code settings.json Deep Dive (Part 2): The Permissions System
A thorough breakdown of Claude Code's permissions configuration — allow/deny/ask rule arrays, wildcard syntax, MCP tool permissions, defaultMode options, and additionalDirectories.
Claude Code settings.json Deep Dive (Part 3): The Hooks System
A thorough breakdown of Claude Code's hooks configuration — four hook types, core events (PreToolUse/PostToolUse/Stop/Notification), stdin/stdout protocol, exit code semantics, and practical examples.
Claude Code settings.json Deep Dive (4): env, Models, Auth, and Other Useful Fields
A comprehensive guide to the remaining settings.json fields in Claude Code — env variable injection, model configuration, authentication helpers, Git attribution, session cleanup, language and UI, thinking depth, auto-updates, memory system, and more.