Repository navigation
Make Claude Sonnet 5.5 the Pro default and Opus opt-in only - #164
Conversation
New Pro accounts start on Sonnet 5.5. Auto Pro routes between Sonnet 5.5 and GPT-6.1 Sol and falls back to Sonnet, so it never picks Opus. Opus runs only when someone selects it. Retired Opus IDs still move to Opus 5.5, since those were explicit picks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reachedEnable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Next included review available in 39 minutes. View limit details
Note 🎁 Summarized by CodeRabbit Free
Comment |
|
The GitHub Actions failures on f31ecb6 did not run the code. Every job stopped within 1 to 2 seconds, and the annotation reads: "The job was not started because recent account payments have failed or your spending limit needs to be increased." It is the repo-wide Actions billing outage. Local results at f31ecb6: |
|
Follow-up data migration for accounts that still have Opus 5.5 saved from the old default: #180. It is stacked on this PR and must be applied after this one is live in production. |
|
Deployment failed for project debatelab-staging with the following error: Learn More: https://vercel.com/adam-gaborjanis-projects?upgradeToPro=build-rate-limit |
… (#180) * Make Claude Sonnet 5.5 the Pro default and Opus opt-in only New Pro accounts start on Sonnet 5.5. Auto Pro routes between Sonnet 5.5 and GPT-6.1 Sol and falls back to Sonnet, so it never picks Opus. Opus runs only when someone selects it. Retired Opus IDs still move to Opus 5.5, since those were explicit picks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Move saved Opus 5.5 settings to Sonnet 5.5 Opus 5.5 was the Pro default, and a saved setting can't tell the default from a pick. This data migration moves every saved Opus 5.5 tool setting to Sonnet 5.5, backs the original rows up in private.opus_default_backup, and skips users it has already migrated. A rollback script restores Opus wherever the migrated Sonnet is still saved. A database test runs both twice against seeded rows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Cover more rollback and stale-client cases in the Opus migration test The test now seeds a tool already on Sonnet before the migration, which the rollback must keep, and an old updated_at, so it fails if the migration stops bumping it. Clients only save their settings cleanup while updated_at is unchanged, so the bump keeps an older client from writing Opus back. agent-stack.sh test now runs the script too, like npm run test:db. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Cost fix 1 of 7. Pro accounts now start on Claude Sonnet 5.5 instead of Claude Opus 5.5, and Opus runs only when someone picks it.
What changes
DEFAULT_PRO_MODELis nowanthropic/claude-sonnet-5.5. New Pro accounts, and Pro accounts that never saved a model, get Sonnet for every tool.claude-sonnet-5,claude-sonnet-4-6) moves to Sonnet 5.5. A saved retired Opus ID (claude-opus-5,claude-opus-4-7) still moves to Opus 5.5, because someone picked Opus on purpose.What this does not change
Existing Pro accounts that already saved Opus 5.5 keep it. The app keeps any saved model that is still in the catalog. The saved row doesn't record whether someone picked Opus or just got it as the old default, so the client can't tell the two apart. Moving those accounts to Sonnet would mean a production data change to
user_settings.feature_configs, which this PR doesn't do. Until then, the savings apply to new accounts, accounts that never saved a model, and every Auto Pro request.This PR doesn't touch the research model, token caps, quotas, prompts, cost logging, or JSON output. Other cost PRs cover those.
Verification (local; GitHub Actions is down repo-wide)
npm run test:edge: 357 passed. The new router test proves that Auto Pro rejects an Opus answer from the router and falls back to Sonnet when the router fails. The handler test now expects Auto Pro to call Sonnet.npm run verify: lint, typecheck, unit, edge, build, service-worker check and 30 desktop Chromium smoke tests all passed.verify-debatelabfake stack,recipes/model-defaultson desktop-chromium and mobile-chromium: 3 of 3 passed on each. A new Pro account'suser_settingshold Sonnet 5.5 for every tool, the selector shows Claude Sonnet 5.5 with Opus 5.5 still enabled, and a Generate run recordsmodel: anthropic/claude-sonnet-5.5inai_requests. Basic accounts still start on Haiku 5.5.I updated the verify skill's recipe and feature notes,
docs/architecture.mdandsupabase/README.mdto match.🤖 Generated with Claude Code