claude-code - 💡(How to fix) Fix Feature request: show timestamps on messages in conversation [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#49079Fetched 2026-04-17 08:51:29
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
labeled ×2commented ×1

This came up during a session with 6 parallel worktree agents, 120+ API calls, and CI waits spanning ~90 minutes. Impossible to tell when things happened without checking external logs.

Root Cause

This came up during a session with 6 parallel worktree agents, 120+ API calls, and CI waits spanning ~90 minutes. Impossible to tell when things happened without checking external logs.

RAW_BUFFERClick to expand / collapse

Problem

During long sessions (30-90+ minutes with background tasks, CI waits, parallel agents), there's no way to see when each message or tool call happened. This makes it hard to:

  • Understand how long a step actually took
  • Correlate chat events with external logs (CI runs, API calls, background processes)
  • Review session history and reconstruct timing

Proposed solution

Add optional timestamps to messages in the conversation view:

  • A setting like showTimestamps: true in settings.json
  • Subtle HH:MM on each message (like Slack hover timestamps)
  • Tool call results already track duration internally — surface it

Context

This came up during a session with 6 parallel worktree agents, 120+ API calls, and CI waits spanning ~90 minutes. Impossible to tell when things happened without checking external logs.

extent analysis

TL;DR

Adding optional timestamps to messages in the conversation view can help users understand the timing of events during long sessions.

Guidance

  • Introduce a showTimestamps setting in settings.json to allow users to opt-in for timestamp display.
  • Display subtle HH:MM timestamps on each message, similar to Slack's hover timestamps, to provide a clear indication of when each message was sent.
  • Consider surfacing the duration of tool call results, which are already tracked internally, to provide additional timing context.
  • Review the proposed solution to ensure it meets the requirements and is feasible to implement, considering factors such as performance and user experience.

Example

No code snippet is provided as the issue does not contain specific implementation details.

Notes

The proposed solution aims to address the issue of understanding timing during long sessions, but its effectiveness may depend on the specific use case and user requirements. Additional considerations, such as handling multiple time zones or providing more detailed timing information, may be necessary.

Recommendation

Apply the proposed workaround by introducing the showTimestamps setting and displaying timestamps on messages, as this addresses the core issue of understanding timing during long sessions.

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