Back to rankings

Claude Code Brings Fast Mode to Remote Sessions

Claude CodeView original changelog

Claude Code 2.1.271, released September 14, 2026, extended fast mode, previously limited to local interactive sessions, to Claude Code Remote sessions running on both Anthropic-managed cloud infrastructure and self-hosted runners. Where an organization's plan and policy allow it, a Remote session now honors the host's fast-mode setting or a /fast command typed directly in the session. The same release also fixed related fast-mode edge cases, including a misleading "Fast mode unavailable" message from /fast off and a retry-watchdog path that kept resending fast requests after the API had already rejected them.

Key Takeaways

  • Fast mode now works in Remote sessions, covering both Anthropic-managed cloud infrastructure and self-hosted runners, not just local interactive CLI use.
  • The toggle is per-session: typing /fast on inside a Remote session turns it on for that session only, without changing the account default.
  • Organization policy still gates access: the feature applies only "where your organization allows it," so admins retain control over the cost exposure it introduces.
  • Fast mode trades cost for speed: per Anthropic's own documentation it runs Claude Opus at up to roughly 2.5x faster output at a higher per-token rate.
  • Three related fast-mode bugs were fixed in the same release: a misleading "unavailable" message from /fast off, repeated re-sending of rejected fast requests, and a retry-watchdog path that failed turns instead of falling back to standard speed.
  • This closes a capability gap between interactive and background Claude Code usage, letting long cloud-side jobs opt into faster, costlier execution for the first time.

Fast Mode Reaches Remote Sessions

Claude Code 2.1.271, released September 14, 2026, extended fast mode to Claude Code Remote sessions, covering both sessions run on Anthropic-managed cloud infrastructure and those run on self-hosted runners. Where an organization's plan and policy allow it, a Remote session now applies the host's fast-mode setting automatically, or a user can type /fast directly inside the session to turn it on or off for that session alone, without changing the account-wide default.

Why It Matters

Fast mode trades a higher per-token cost for substantially quicker output on Claude Opus, a tradeoff that pays off most on long-running generation such as large diffs, multi-file migrations, or detailed written analysis. Until this release, that option was unavailable to background agents and self-hosted-runner jobs, so long remote tasks always ran at standard speed regardless of urgency. Extending fast mode to Remote sessions gives teams the same speed-for-cost choice for cloud-side work that interactive CLI sessions already had.

Related Fixes Shipped Alongside It

Version 2.1.271 also patched a handful of narrower fast-mode bugs discovered as the feature matured. /fast off no longer answers "Fast mode unavailable" when an organization has simply disabled fast mode rather than never having enabled it. Sessions started with the CLAUDE_CODE_SKIP_FAST_MODE_ORG_CHECK flag stopped re-sending fast-mode requests every turn after the API had already rejected the request once, and fast mode running under CLAUDE_CODE_RETRY_WATCHDOG no longer fails a turn outright on a usage-credits limit or silently retries an overload at fast speed; it now falls back to standard speed as intended.

Rollout Details

Access remains gated by organization policy, so the feature will not appear for every account immediately. Anthropic's own fast-mode documentation notes the feature can run Opus at up to roughly 2.5x its normal output speed at a correspondingly higher rate per token, which is the same tradeoff now available to Remote sessions.