claude-code - 💡(How to fix) Fix Feature request: display 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#46275Fetched 2026-04-11 06:24:37
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
1
Timeline (top)
labeled ×3commented ×1

Fix Action

Fix / Workaround

Workarounds considered

RAW_BUFFERClick to expand / collapse

Problem

There is no way to see when messages were sent or received in a Claude Code conversation — neither user prompts nor assistant responses display timestamps. This applies to all three clients: CLI (terminal), IDE extensions (VS Code / JetBrains), and the web app (claude.ai/code).

Why timestamps matter

When working on multi-hour sessions or reviewing a conversation after the fact, temporal context is critical:

  • Referencing past interactions: "the thing we discussed this morning" has no anchor point without timestamps
  • Debugging agent behavior: when investigating autonomous agent issues (cron jobs, scheduled tasks), correlating conversation events with external logs requires knowing when each exchange happened
  • Multi-device workflows: users who switch between terminal, phone, and IDE throughout the day lose all sense of timeline
  • Context for AI: if the AI could see when messages were sent, it could better reason about recency, urgency, and temporal relationships between events the user describes

Workarounds considered

  • CLI hook (user-prompt-submit): can log timestamps to a file, but doesn't display them inline in the conversation — and doesn't cover IDE or web clients
  • Prefixing messages manually: impractical and doesn't timestamp the AI's responses
  • No config option exists across any of the three clients to enable this

Proposal

Display a subtle timestamp (e.g., 14:32 or 2:32 PM depending on locale) next to each message — both user prompts and assistant responses. This is standard in virtually every chat interface (Slack, Discord, iMessage, etc.) and its absence in Claude Code is a notable gap.

Ideally configurable (show/hide) for users who prefer a clean view.

extent analysis

TL;DR

Displaying timestamps next to each message in Claude Code conversations is the most likely fix to provide temporal context.

Guidance

  • Consider adding a timestamp display option to the configuration settings of all three clients (CLI, IDE extensions, and web app) to allow users to choose whether to show or hide timestamps.
  • Implementing a subtle timestamp format (e.g., 14:32 or 2:32 PM) next to each message, including both user prompts and assistant responses, would provide the necessary temporal context.
  • To ensure consistency across different locales, use a locale-dependent timestamp format.
  • Evaluate the feasibility of integrating the user-prompt-submit CLI hook to display timestamps inline in the conversation, potentially extending this functionality to IDE and web clients.

Example

No explicit code example is provided due to the lack of specific technical details in the issue.

Notes

The proposal to display timestamps is based on the importance of temporal context in conversations, as highlighted in the issue. However, the technical implementation details are not specified, and the feasibility of integrating this feature across all clients is uncertain.

Recommendation

Apply a workaround by implementing a configurable timestamp display option, as this would provide users with the necessary temporal context while allowing for a clean view if preferred.

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 Feature request: display timestamps on messages in conversation [1 comments, 2 participants]