claude-code - 💡(How to fix) Fix [FEATURE] Show conversation duration / elapsed time [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#47844Fetched 2026-04-15 06:40:44
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
labeled ×2commented ×1

Error Message

error-prone and easy to forget. There is no built-in workaround.

Fix Action

Fix / Workaround

Currently I manually check the clock before and after a session, which is error-prone and easy to forget. There is no built-in workaround.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

When working on longer conversations or tasks in Claude Code, I have no way to know how much time has elapsed in the current session. This makes it difficult to track time spent on a task — for personal productivity, client billing, or general awareness.

Proposed Solution

Show elapsed time for the current conversation somewhere in the Claude Code UI — for example in the status bar or conversation header. Ideally a simple timer that starts when the conversation begins and shows hours:minutes.

Alternative Solutions

Currently I manually check the clock before and after a session, which is error-prone and easy to forget. There is no built-in workaround.

Alternative proposed solution: show time next to the message when I sent it.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

  1. I start a Claude Code session to work on a feature
  2. I get into the flow and lose track of time
  3. At some point I want to know how long I've been working
  4. With this feature I could glance at the timer in the UI without leaving the conversation or checking external tools
  5. This would help with time tracking for billable work or just personal productivity awareness

Additional Context

No response

extent analysis

TL;DR

Implementing a timer that displays elapsed time since the start of a conversation in the Claude Code UI would address the issue.

Guidance

  • Consider adding a timestamp when a conversation begins and calculate the elapsed time to display in the UI.
  • The timer could be placed in the status bar or conversation header for easy visibility.
  • An alternative approach could be to display the time next to each message, allowing users to track time spent on specific parts of the conversation.
  • To verify the effectiveness of the solution, test the feature with various conversation scenarios, including long and short sessions.

Example

No code example is provided as the issue does not contain specific technical details about the implementation.

Notes

The solution's feasibility and implementation details may depend on the existing architecture and technical stack of Claude Code, which is not specified in the issue.

Recommendation

Apply workaround: Implement a simple timer in the UI to display elapsed time since the conversation started, as this directly addresses the user's need for time tracking without requiring significant changes to the existing functionality.

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