[BUG] Claude should never guess the current time — always check system clock
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?
## Problem
Claude estimates the current time based on conversation length instead of checking the system clock. When helping users manage schedules, prep for meetings, or plan their day, Claude states times like
"it's 6:35" when it's actually 6:25 — creating false urgency and eroding trust.
This happened to me over 30+ messages in a single session. I told Claude it was 5:34 AM. Over the next hour it kept inflating: "6:05", "6:15", "6:25", "6:35" — all wrong, all guesses.
## Expected behavior
Any time Claude references the current time, it should run date (or equivalent system command) first. If it can't check, it should not state a time.
## Impact
Every user who asks Claude to help with scheduling, meeting prep, time management, or daily planning is affected. Time awareness is fundamental to being a useful assistant. Guessing undermines the core
value proposition.
## Suggested fix
Add to Claude's base behavior: never state or estimate the current time without verifying via system clock. This applies to Claude Code, Claude Desktop, and any context where system time is accessible.
What Should Happen?
its included
Error Messages/Logs
When Claude references the current time in any context (Claude Code, Desktop,
or any environment with system access), it should execute a system clock check
(`date` command or equivalent) BEFORE stating the time. If it cannot verify the
time, it should not state one.
Time references like "it's 6:35, go shower" should only appear after verification.
Estimates based on conversation length are never acceptable.
Steps to Reproduce
Steps to reproduce
- Open a Claude Code session
- Tell Claude what time it is (e.g., "it's 5:34 AM")
- Have a long conversation (30+ messages over ~50 minutes)
- Observe Claude stating increasingly inflated times ("6:05", "6:15", "6:25",
"6:35") without ever running date to verify
- When challenged, Claude admits it was guessing
## Problem
Claude estimates the current time based on conversation length instead of
checking the system clock. When helping users manage schedules, prep for
meetings, or plan their day, Claude states wrong times — creating false
urgency and eroding trust.
In my case, Claude was off by 10+ minutes over the course of a session,
telling me I was running late when I actually had plenty of time.
## Impact
Every user who asks Claude to help with scheduling, meeting prep, time
management, or daily planning is affected. Time awareness is fundamental
to being a useful assistant. Guessing undermines the core value proposition.
## Suggested fix
Add to Claude's base behavior: before stating or referencing the current time,
always verify via system clock. The date command is available in Claude Code.
In other contexts, use whatever time source is available. If none is available,
do not state a time — say "you should go soon" not "it's 6:35."
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.143
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗