claude-code - 💡(How to fix) Fix Feature request: show absolute timestamps in inline status lines (not just elapsed duration) [2 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#60531Fetched 2026-05-20 03:56:10
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1cross-referenced ×1

Root Cause

Real workflow: developers running 10+ Claude Code instances across projects often lose track of which session was last active and when. Sessions can also span days (left idle overnight, resumed next morning). A full wall-clock timestamp solves orientation instantly without needing to glance at the system clock or compute "8 minutes ago from when?" — and without ambiguity about which day an event happened.

Fix Action

Fix / Workaround

Workarounds tried

RAW_BUFFERClick to expand / collapse

Problem

When working with multiple Claude Code sessions in parallel across many terminals, the inline status indicators show only elapsed duration:

✻ Brewed for 50s
Worked for 8m 14s
● Mark task #6 complete.

This makes it hard to orient in time after switching between consoles. "Worked for 8m 14s" tells me how long something took, but not WHEN it happened. After switching back to a terminal that's been idle for a while, I can't tell at a glance whether the last action was 2 minutes or 2 hours ago — and "8 minutes from when?" is impossible to answer without context. Worse, sessions often span multiple days (left running overnight, picked up next morning), so a pure clock time like 14:22 is also ambiguous.

Proposed solution

Add a setting (e.g. "timestampFormat": "absolute" | "duration" in settings.json, or a CLI flag) that switches inline indicators to absolute wall-clock timestamps with full date:

✻ Brewed at 2026-05-19 14:22
Worked at 2026-05-19 14:22 (took 8m 14s)
● Mark task #6 complete at 2026-05-19 14:30

Format YYYY-MM-DD HH:MM is preferred over just HH:MM:SS because sessions frequently span multiple days. Either replacing the elapsed duration entirely, or appending the wall-clock timestamp alongside it, would work.

Why this matters

Real workflow: developers running 10+ Claude Code instances across projects often lose track of which session was last active and when. Sessions can also span days (left idle overnight, resumed next morning). A full wall-clock timestamp solves orientation instantly without needing to glance at the system clock or compute "8 minutes ago from when?" — and without ambiguity about which day an event happened.

Workarounds tried

  • Custom status line with date — shows current time, but not the time of each past action.
  • showTurnDuration: false — hides the duration but doesn't replace it with anything useful.

Neither addresses the actual need: knowing when each step happened.

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: show absolute timestamps in inline status lines (not just elapsed duration) [2 comments, 2 participants]