Hi! I understand your Claude app wallet hasn't reset even after 24 hours and that this is a recurring problem for you. Just to get a clearer picture before we dive into solutions—are you referring to the wallet’s usage limit or token balance not refreshing after a specific period? Also, are you on the free or pro plan? Any details on what steps you’ve already tried would be useful too.

Meanwhile, from what I’ve seen, there are some known issues where the Claude app wallet or usage limits do not reset on time, sometimes not even after many hours. This has been reported by other users and might relate to how the app tracks token usage or session boundaries. Sometimes, the limits only reset after fully reaching 100% usage or after a specific server-side update cycle1.

Here’s a step-by-step approach to possibly resolve or better understand this:

1. Check Account Status
Log out and then back in to your Claude app. This can refresh your session and wallet status.

2. Verify Your Usage
Confirm if your wallet is truly empty or if it still shows some balance/tokens. Sometimes, the UI might misrepresent the state due to syncing issues.

3. Wait for the Reset Time Window
Usually, limits or wallet balances reset every 24 hours, but this can vary depending on your subscription plan (free vs pro) or app version. If your wallet didn’t reset after 24 hours this time, it could be a temporary server-side lag.

4. Clear Cache or Restart App/Device
Sometimes, residual app data might cause display or sync issues. Try clearing the app cache or fully restarting your device.

5. Check for App Updates
Ensure your Claude app is updated to the latest version. Sometimes, bugs with wallet resets are fixed in new releases.

6. Review Known Issues
There are open reports and discussions where users experience wallet/limit resets not happening on time, especially if the session limit or weekly limit is involved. Sometimes, the app awaits a full 100% usage before triggering a reset1 2.

If after these you still face the issue, it could be a bug or server-side condition requiring developer attention. Let me know what you observe after trying these steps, and if needed, I can guide you on reporting the issue or escalating it.

Does that sound okay to start with?