Feature Request: API Fallback for Pro/Max Subscriptions When Limits Are Reached

I just purchased a max plan and, upon finding that this functionality does not already exist, am deeply frustrated.

I just purchased a max plan and, upon finding that this functionality does not already exist, am deeply frustrated.

Yesterday, I learned that it actually does kind of exist, but is not the most intuitive.

Without exiting, you can type in /login to the prompt, login with your API/console account, and then resume the conversation, but then you have to go through the same process to switch back to your subscription account.

> I just purchased a max plan and, upon finding that this functionality does not already exist, am deeply frustrated. Yesterday, I learned that it actually does kind of exist, but is not the most intuitive. Without exiting, you can type in /login to the prompt, login with your API/console account, and then resume the conversation, but then you have to go through the same process to switch back to your subscription account.

Thank you! I can confirm that this works on my end as well. I still firmly believe auto-switching should be configurable as a core feature but this flow dramatically eases the pain. Thank you

I was just trying to figure this out myself, too. I came up with the login solution, but it's a pain. There are periods when you are getting things done and you just need to finish.

Thank you for flagging this. We will have an update on this soon.

Would love to see auto-switching implemented!

Just upgraded to Max 5x and hit this after a long bout of coding. Definitely want this improvement to make it seamless to fallback to API billing.

Not having this option is very frustrating. It's keeping users from giving you money, hard to understand how this can take weeks or months to implement.

Really should be default if a user have api and a plan configured. It should switch back automatically as well.

+1 to this feature request! While the proposed API fallback to Claude's native API is valuable, I'd like to suggest extending this functionality to support Amazon Bedrock as well. This would be particularly beneficial for enterprise customers who have procured Claude for Enterprise through AWS Marketplace.

The seamless fallback to Bedrock would align well with the original proposal's goals of maintaining uninterrupted workflows, while also accommodating organizations that have standardized on AWS services. This could be implemented as an additional authentication option in the suggested configuration:

{
  "fallback": {
    "enabled": true,
    "provider": "bedrock", // or "claude_api"
    "aws_credentials": {}, // for Bedrock
    "api_key": "sk-ant-api03-...", // for Claude API
    "auto_switch": false,
    "prompt_before_switch": true
  }
}

This would provide more flexibility for enterprise users while maintaining the same seamless experience described in the original feature request.

I can confirm that the /login option and switching to API billing does work, but it is VERY EXPENSIVE, on the order of $5 per hour - it would great if the program reported the API usage and / or token usage, so that users could judge whether they are getting good value for their money.

@catherinewu Any word on this? I'd really like to subscribe to Pro but this limitation is holding me back.

I mean, if we need to keep logining in to switch, at least don force us to copy and paste login api key all the time, save login credetials, at least.

Issue raised in July wtf are they doing...They are leaving huge money on the table for something that would take them 20 min to implement....(Especially considering the fact that using API key is so expensive compared to using a plan...Yes, I was using API only before getting a plan and with the API I was burning so much money, it was like 20-30x the cost of using a plan something like that). So guys, hurry up, you can literally multiply your investor money in 20min lol

It's wild there are no updates on this. It completely stops work when the model just hangs mid-execution, you can't do much even manually or with another model unless reverting to previous commit.

Incredibly frustrating, and by far the worst part about Claude code.

I really would have hoped Anthropic would do better here, seems like a major issue a lot of people are complaining about. Feels like they want to push users to higher subscriptions intentionally.

Hi everyone - we now support Pro/Max users configuring extra usage on https://claude.ai/settings/usage so that you can continue your session at API price. We'll switch you back to your subscription when your rate limit resets.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.