[BUG] Old conversation sessions still rate-limited after upgrading from Pro to Max plan (macOS desktop app)

Resolved 💬 3 comments Opened Mar 26, 2026 by JiaChen430 Closed Mar 29, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

After upgrading from Claude Pro to Claude Max plan, old/existing conversation sessions in the macOS desktop app still show "rate limit hit" and refuse to send any messages. New conversation sessions work fine with Max plan limits.

Steps to reproduce:

  1. Have an active conversation session in the Claude macOS desktop app on the Pro plan
  2. 2. Hit the Pro plan rate limit in that session
  3. 3. Upgrade from Pro to Max plan
  4. 4. Go back to the same old conversation session and try to send a message

Expected behavior:
The old session should recognize the upgraded Max plan and allow sending messages, since Settings shows 0% usage.

Actual behavior:
The old session continues to show "rate limit hit" and blocks all messages. Even after:

  • Force quitting and reopening the app (app correctly shows "Max plan")
  • - Signing out and signing back in
  • - - The old session still refuses to accept messages

New sessions created after the upgrade work correctly with Max plan limits.

Environment:

  • Claude macOS desktop app (latest version)
  • - macOS
  • - - Upgraded from Pro to Max plan

What Should Happen?

After upgrading plans, all existing conversation sessions should immediately reflect the new plan's rate limits. The rate limit state should be refreshed when the app detects a plan change, without requiring the user to start a new conversation and lose their project context.

Error Messages/Logs

Steps to Reproduce

  1. Open the Claude macOS desktop app and start a conversation on the Pro plan
  2. 2. Use the conversation until you hit the Pro plan rate limit
  3. 3. Upgrade your subscription from Pro to Max plan
  4. 4. Return to the same old conversation session
  5. 5. Try to send any message
  6. 6. Observe: the old session still says rate limit hit, even though Settings > Usage shows 0% used
  7. 7. Open a new conversation - it works fine with Max limits
  8. 8. Try force-quitting and reopening the app - old session still blocked
  9. 9. Try signing out and signing back in - old session still blocked

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

N/A - This bug is about the Claude macOS desktop app, not Claude Code CLI

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗