Time-aware session resumption

Resolved 💬 3 comments Opened Jan 13, 2026 by psoup1965 Closed Feb 27, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When significant time passes between messages (hours/days), Claude Code should
proactively acknowledge the gap and ask if anything changed, rather than
continuing as if no time passed.

Currently, Claude has no apparent awareness of time gaps. After a long-running
task (compilation, indexing, etc.) or returning the next day, the AI continues
as if the user never left. This feels mechanical and misses context that may
have changed.

Proposed Solution

  • Detect when time since last message exceeds a threshold (e.g., 30+ minutes)
  • Proactively ask: "It's been a while - did anything change? Did the task complete?"
  • Offer options: Yes/No/Not sure
  • If "yes" or "not sure," offer to re-check relevant state (files, git status, etc.)

## Why This Matters
Humans experience time. Waiting 45 minutes for an index to run feels long.
Acknowledging that gap makes the interaction more human and catches context
changes before they cause confusion.

## Similar Behavior
Claude Code already refreshes codebase knowledge at session start. This extends
that concept to mid-session gaps.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

  • Detect when time since last message exceeds a threshold (e.g., 30+ minutes)
  • Proactively ask: "It's been a while - did anything change? Did the task complete?"
  • Offer options: Yes/No/Not sure
  • If "yes" or "not sure," offer to re-check relevant state (files, git status, etc.)

Additional Context

Believe it or not, this stems from a late night chat with claude while waiting for files to index.

View original on GitHub ↗

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