Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Feature request: inline message timestamps [1 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#60711•Fetched 2026-05-20 03:51:30
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
mralexashtonmralexashton
Participants
mralexashtonmralexashton
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Feature Request

Add optional inline timestamps to messages in Claude Code conversations.

Use Case

When running long-lived Claude Code sessions (especially via orchestration tools like agent-deck where sessions persist for days/weeks), it's very useful to know when messages were sent from both sides — user and assistant.

Currently the only time-related display is showTurnDuration which shows turn processing time, but not actual wall-clock timestamps.

Proposed Behavior

  • Optional setting (e.g., showTimestamps: true in settings.json)
  • Displays a timestamp (e.g., May 19 14:32) next to each user and assistant message
  • Useful for:
    • Long-running sessions that span hours/days
    • Multi-session orchestration where you switch between sessions
    • Debugging timing issues
    • Reviewing conversation history

Alternatives Considered

  • Hook-based logging to a side file (works but loses the inline benefit)
  • showTurnDuration (shows duration, not wall-clock time)

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…
#conversation history#runtime error#dependency conflict#environment setup#docker error

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: inline message timestamps [1 participants]