claude-code - 💡(How to fix) Fix Add time context to assistant prompts (timestamp or time-since-last-message) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46325Fetched 2026-04-11 06:23:15
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×2closed ×1commented ×1

The assistant currently receives the date but has no sense of time passing between messages. This leads to awkward interactions where the assistant has no idea if 30 seconds or 30 minutes have passed since the last exchange — resulting in poorly timed follow-ups and no ability to reason about durations.

Root Cause

The assistant currently receives the date but has no sense of time passing between messages. This leads to awkward interactions where the assistant has no idea if 30 seconds or 30 minutes have passed since the last exchange — resulting in poorly timed follow-ups and no ability to reason about durations.

RAW_BUFFERClick to expand / collapse

Description

The assistant currently receives the date but has no sense of time passing between messages. This leads to awkward interactions where the assistant has no idea if 30 seconds or 30 minutes have passed since the last exchange — resulting in poorly timed follow-ups and no ability to reason about durations.

Proposal

Add a lightweight time signal to each message, either:

  • A timestamp: [2026-04-11 14:32:07] (~8 tokens)
  • Time since last message: [3m] (~1 token)

The minimal option ([3m]) is preferred as it's essentially free in terms of token cost while solving the core problem.

Use cases

  • Knowing whether a long-running process (file copy, build, deploy) is likely still in progress
  • Avoiding premature follow-ups ("how's that going?" after 20 seconds)
  • Better conversational pacing and temporal reasoning
  • Providing more useful time-based estimates and suggestions

Impact

Near-zero token cost, significant improvement in conversational awareness and interaction quality.

extent analysis

TL;DR

Adding a lightweight time signal, such as a timestamp or time since last message, to each message can improve the assistant's conversational awareness and interaction quality.

Guidance

  • Consider adding a time signal to each message, with the minimal option of including the time since the last message ([3m]) being preferred due to its low token cost.
  • Evaluate the trade-offs between using a full timestamp ([2026-04-11 14:32:07]) versus the minimal time since last message ([3m]) based on specific use cases and requirements.
  • Assess how the addition of time signals can enhance the assistant's ability to reason about durations and improve conversational pacing.
  • Review the potential impact of this change on the overall interaction quality and user experience.

Example

No explicit code example is provided as the issue focuses on the conceptual approach rather than specific implementation details.

Notes

The effectiveness of this solution may depend on the specific requirements and constraints of the application, including token cost limitations and the need for precise timing information.

Recommendation

Apply the workaround of adding a lightweight time signal to each message, preferably using the minimal option of time since last message ([3m]), as it offers a significant improvement in conversational awareness with near-zero token cost.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Add time context to assistant prompts (timestamp or time-since-last-message) [1 comments, 2 participants]