Feature Request: Time awareness and temporal feedback loop for better task estimation

Resolved 💬 3 comments Opened Feb 10, 2026 by goettemar Closed Feb 14, 2026

Problem

Claude currently has no sense of time beyond the current date. This leads to several practical issues:

1. No contextual time awareness

  • Claude says "Good evening" when it's morning
  • Statements like "let's continue later" can't be interpreted correctly (later today vs. tomorrow depends on current time)
  • No ability to adjust communication style based on time of day

2. No task duration estimation capability

Despite having processed millions of similar tasks across sessions worldwide, Claude cannot provide reliable time estimates because:

  • There is no feedback loop between estimated vs. actual task duration
  • Each session starts from zero — like a developer with 10 years of experience who pretends they've never estimated a task before
  • Aggregated, anonymized data about actual task durations across sessions is not utilized

Proposed Solution

Minimal (low effort, high impact):

  • Include current local time in the system context (trivial to implement, costs nothing)
  • This alone would fix greetings, contextual interpretation of temporal references, and session-aware responses

Advanced (high impact for professional users):

  • Aggregate anonymized task duration data across sessions (e.g., "PySide6 feature with DB integration typically takes X hours")
  • Implement a feedback loop: estimated vs. actual duration tracking
  • Use this data to provide increasingly accurate time estimates over time
  • This would be especially valuable for teams doing sprint planning and project management

Why This Matters

A human developer intuitively knows:

  • "This refactoring will take about 2 hours" (based on past experience)
  • "Let's continue this afternoon" means something different at 9 AM vs. 10 PM
  • How to adjust communication and planning based on time of day

Claude has access to far more data points than any individual developer but currently cannot leverage any of them for temporal reasoning. This is a significant gap between capability and implementation.

Impact

  • Better UX through time-appropriate communication
  • More reliable project planning when using Claude for development tasks
  • Competitive advantage for professional/enterprise users
  • Minimal implementation cost for the basic time awareness feature

---
Submitted on behalf of a Claude Max user who works extensively with Claude Code on multiple software projects.

View original on GitHub ↗

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