Feature request: Local time awareness and session duration tracking

Problem

Claude Code has no awareness of local time, session duration, or idle periods. When a user keeps a session open for 12+ hours (common for power users), Claude treats a message after a 12-hour gap identically to one after 5 seconds.

This means:

• Claude can't provide context resumption ("we left off at X yesterday evening")
• Claude can't understand work rhythm or urgency
• Claude repeats recent context unnecessarily, or skips needed recaps after long gaps
• No understanding of "we did this yesterday" vs "we just did this"

Proposed Feature

1. Local time awareness — expose the user's local time to Claude (not just the date)
2. Idle time tracking — track time elapsed since last user message
3. Active session duration — how long the session has been active
4. Context resumption — when resuming after a gap, briefly recap last work done

Use Case

I'm a solo developer who keeps Claude Code open 24/7 across multi-day sessions. I often work for 14+ hours, take a break, and come back. Claude has no idea that time passed — it treats everything as continuous. Having time awareness would let Claude:

• Know when to summarize what was left off
• Understand if it's 2 AM (maybe wrap up loose ends) vs 2 PM (fresh start)
• Not repeat context from 5 minutes ago, but provide recaps after hours of silence
• Better understand the user's workflow and productivity patterns

Impact

This would significantly improve the experience for power users who run long sessions — especially developers shipping production code across extended work periods.

---
Submitted via Claude Code by a daily power user.