Feature request: real-time clock awareness
Resolved 💬 3 comments Opened Mar 2, 2026 by sirlund Closed Mar 6, 2026
Feature Request
Claude Code has no awareness of the current real time. It can only infer time from command outputs (like date), but doesn't proactively know what time it is.
Problem
When a conversation spans multiple hours or resumes the next day, Claude makes incorrect assumptions about the time. For example:
- A timer recorded
23:44during a session - The next morning at 9 AM, the user asks "do you know what time it is?"
- Claude assumes it's still midnight based on the last timestamp it saw
Expected behavior
Claude Code should have ambient awareness of the current time (at least at the start of each turn), similar to how it receives the current date. This would help with:
- Appropriate greetings ("good morning" vs "buenas noches")
- Estimating elapsed time since last interaction
- Not making wrong assumptions about session continuity
Current workaround
Run date manually, but Claude doesn't do this proactively.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗