[FEATURE] Allow downgrade to previous version when current model has problems

Status Closed — not planned
Maintainer reply None cached
Activity 1 comment · opened Jun 24, 2026 · closed Aug 8, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I can't switch to a previous opus version when the current opus version is having problems. For example right now opus 4.8 is having problems, but my team account only lists the latest opus 4.8 or sonnet 4.6/haiku4.6 as available, while opus 4.7 is not having problems. So I either have to use Sonnet 4.6 or wait for Anthropic support to fix the Opus 4.8 problem.

Proposed Solution

It would be nice to have the ability to move to a previous version when outages occur. I don't know if this is a rule for Team accounts or not.

Alternative Solutions

I used Gemini and OpenAI when the Opus model was down.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

Working in Claude Code when Claude model hangs.

Additional Context

Claude Code Extension in vscode hangs and can't be stopped when the Claude model hangs (like most Claude Opus 4.x issues reported in status.claude.com. That problem should also be added as a bug ticket.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗