claude-code - 💡(How to fix) Fix [Bug] Weekly usage reset time displayed incorrectly for Pro plan users

[{"error":"Error: Failed to fetch version from https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/latest: ECONNREFUSED\n at zF1 (/$bunfs/root/src/entrypoints/cli.js:2749:5253)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T15:04:38.734Z"},{"error":"Error: Failed to fetch version from https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/latest: ECONNREFUSED\n at zF1 (/$bunfs/root/src/entrypoints/cli.js:2749:5253)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T15:04:38.734Z"},{"error":"Error: EISDIR: illegal operation on a directory, read '/Users/brandontaylor/Documents/CMU/CAPSTONE/Dark_Circle/crl-train/tests/data'\n at nKH (/$bunfs/root/src/entrypoints/cli.js:1564:144)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T15:46:46.081Z"},{"error":"Error: EISDIR: illegal operation on a directory, read '/Users/brandontaylor/Documents/CMU/CAPSTONE/Dark_Circle/crl-train/training'\n at nKH (/$bunfs/root/src/entrypoints/cli.js:1564:144)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T15:50:05.697Z"}]

TL;DR

The weekly usage reset time may be incorrectly displayed due to the rolling 7-day window reset mechanism, and the user's continued usage is causing the reset time to shift.

Guidance

• The issue might be related to the rolling 7-day window reset mechanism, which can cause the "resets by" time to change as the user continues to use the service.
• To verify the correct reset time, the user can try to stop using the service for a period and observe if the reset time stabilizes.
• The user can also try to check the reset time at different intervals to see if it changes as expected.
• It's possible that the reset time is being updated incorrectly due to the user's usage patterns, and further investigation is needed to determine the root cause.

Example

No code snippet is provided as the issue is related to the service's behavior and not a specific code problem.

Notes

The issue is specific to the Pro plan and the user's usage patterns, and more information may be needed to fully understand the root cause. The provided error logs do not seem to be directly related to the issue.

Recommendation

Apply workaround: The user can try to stop using the service for a period and observe if the reset time stabilizes, or check the reset time at different intervals to see if it changes as expected. This can help to mitigate the issue until the root cause is determined.