[BUG] Claude CLI does not correctly detect timezone

Resolved 💬 3 comments Opened Mar 14, 2026 by martinbean Closed Mar 18, 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?

Claude CLI does not correctly detect timezone. It says I have hit my limit, and that limit resets "12pm (Europe/London)", but it is not 12:58pm here in the UK. I'm guessing this is related to the US recently entering DST, but the UK has not yet, so is an hour out.

What Should Happen?

If Claude is saying my timezone resets 12pm in Europe/London timezone, then I should have been able to use Claude for the past hour.

Error Messages/Logs

> You've hit your limit · resets Mar 15 at 12pm (Europe/London)

Steps to Reproduce

  1. Subscribe to Claude Pro.
  2. Install Claude CLI.
  3. Do lots of things to use your weekly session limit.
  4. Try and use Claude CLI at the time it says that limit resets.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.76 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Warp

Additional Information

<img width="492" height="52" alt="Image" src="https://github.com/user-attachments/assets/f8976706-17d5-4011-826f-8fbaa5131316" />

View original on GitHub ↗

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