Anthropic's flagship Opus at up to 2.5x output speed for latency-sensitive long-horizon coding and agent workflows.
Output Speed *
Intelligence Index *
Context Window *
Input price
Output price
Performance
Where Fast Mode Actually Helps: Long Output Streaming
Benchmarks
Fast Mode Inherits Standard Opus 4.8 Coding Scores
Output Speed
Intelligence Index
MMLU *
GPQA *
HLE *
LiveCodeBench *
Technical Specifications
What the model supports
Limitations & Trade-offs
Best-Fit Workloads
Where this model earns its place
Interactive coding and live debugging
Fast mode's throughput gain is most valuable when an engineer is watching output stream. Toggle it on with /fast when you need speed for interactive work like rapid iteration or live debugging, and off when cost matters more than latency. Long code edits arrive faster, keeping developers in flow. Since quality equals standard Opus 4.8's strong coding scores, there is no capability trade-off—only cost.
Latency-sensitive agent UIs
For user-facing agents that generate long transcripts or multi-step plans, faster streaming reduces perceived wait. Because tool calling is meaningfully more efficient, using fewer steps for the same intelligence, combining Opus 4.8's agentic efficiency with fast serving improves responsiveness in interactive deployments. Note the unchanged TTFT means the first token still arrives at standard latency.
Long-form generation with a human in the loop
Drafting long documents, detailed analyses, or large refactors where someone reviews output as it streams benefits directly from higher output tokens per second. The advantage scales with output length, so short answers gain little. Treat fast mode as a per-session choice enabled when long generation is expected, then disabled to control spend.
Rapid prototyping of agentic pipelines
During development of long-horizon agent workflows, faster iteration shortens the feedback loop when engineers actively observe runs. Fast mode's identical behavior to standard Opus 4.8 means prototypes translate cleanly to production on standard serving. Because it is a research preview with shared rate limits, avoid depending on 2.5x throughput for scaled, unattended production runs.