[BUG] Desktop app shows "소진 (exhausted)" despite remaining usage on Windows

Resolved 💬 2 comments Opened Apr 18, 2026 by sambuza Closed Apr 21, 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?

Subject: Desktop App Shows "Weekly Usage Exhausted" Error Despite Remaining Quota

Description:
I'm experiencing a usage limit issue that only occurs on the Claude desktop app, while the web version works normally.

Issue:
- The desktop app displays "주가 사용량 소진" (Weekly usage exhausted) warning
- However, my actual usage shows plenty of remaining quota:
  • Current Session: 8% used
  • Weekly Limit: 15% used
  • Sonnet Model: 2% used
  • Claude Design: 0% used

Environment:
- Platform: Desktop app
- Web version: Works normally with no issues
- Usage appears correct in web interface

Steps Taken:
- Verified usage in web interface (quota available)
- Error only occurs in desktop app
- Appears to be a data synchronization issue between web and desktop

Expected Behavior:
Desktop app should reflect the same usage data as the web interface and allow continued usage with remaining quota.

Attachments:
[Screenshots showing usage dashboard and the error message]

이렇

<img width="1032" height="498" alt="Image" src="https://github.com/user-attachments/assets/1eba5ea3-1a49-4b3e-a094-211ab785922b" />

What Should Happen?

Subject: Desktop App Shows "Weekly Usage Exhausted" Error Despite Remaining Quota

Description:
I'm experiencing a usage limit issue that only occurs on the Claude desktop app, while the web version works normally.

Issue:
- The desktop app displays "주가 사용량 소진" (Weekly usage exhausted) warning
- However, my actual usage shows plenty of remaining quota:
  • Current Session: 8% used
  • Weekly Limit: 15% used
  • Sonnet Model: 2% used
  • Claude Design: 0% used

Environment:
- Platform: Desktop app
- Web version: Works normally with no issues
- Usage appears correct in web interface

Steps Taken:
- Verified usage in web interface (quota available)
- Error only occurs in desktop app
- Appears to be a data synchronization issue between web and desktop

Expected Behavior:
Desktop app should reflect the same usage data as the web interface and allow continued usage with remaining quota.

Attachments:
[Screenshots showing usage dashboard and the error message]

이렇

<img width="1032" height="498" alt="Image" src="https://github.com/user-attachments/assets/1eba5ea3-1a49-4b3e-a094-211ab785922b" />

Error Messages/Logs

Steps to Reproduce

Subject: Desktop App Shows "Weekly Usage Exhausted" Error Despite Remaining Quota

Description:
I'm experiencing a usage limit issue that only occurs on the Claude desktop app, while the web version works normally.

Issue:
- The desktop app displays "주가 사용량 소진" (Weekly usage exhausted) warning
- However, my actual usage shows plenty of remaining quota:
  • Current Session: 8% used
  • Weekly Limit: 15% used
  • Sonnet Model: 2% used
  • Claude Design: 0% used

Environment:
- Platform: Desktop app
- Web version: Works normally with no issues
- Usage appears correct in web interface

Steps Taken:
- Verified usage in web interface (quota available)
- Error only occurs in desktop app
- Appears to be a data synchronization issue between web and desktop

Expected Behavior:
Desktop app should reflect the same usage data as the web interface and allow continued usage with remaining quota.

Attachments:
[Screenshots showing usage dashboard and the error message]

이렇

<img width="1032" height="498" alt="Image" src="https://github.com/user-attachments/assets/1eba5ea3-1a49-4b3e-a094-211ab785922b" />

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.113 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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