[FEATURE] Session Time Tracking (Daily / Weekly / Monthly Summary)

Resolved 💬 3 comments Opened Nov 26, 2025 by ROTEMIL95 Closed Jan 26, 2026

Preflight Checklist

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

Problem Statement

Right now, Claude Code doesn’t provide any built-in way to see how much time I’ve actually spent coding in a session, during the current day, or over longer periods like a week or a month.

As a developer, I often want to understand:

  • How long it really takes me to develop a specific feature
  • How much time I’ve worked today across different projects
  • Whether I’m becoming faster or more efficient over time

This is especially important for:

  • Freelancers and contractors who need to bill accurately for their time
  • Independent developers who want to price their work correctly
  • Beginners and students who want to track their learning and improvement

Without this feature, I have to rely on rough guesses or external tools, and there’s no direct connection between my coding time and my actual work inside Claude Code.

Proposed Solution

I’d like Claude Code to include Session Time Tracking with automatic aggregation over different time ranges.

Ideally, the feature would:

  • Track active coding time in:
  • The current session
  • Today
  • This week
  • This month
  • Show an optional summary at the end of a session or at the end of the day, for example:

“You’ve been coding for 2h 47m today.”

  • Provide a simple place in the UI (for example, a small panel, status bar item, or command palette entry) where I can quickly see:
  • Session time
  • Today’s total time
  • This week’s total time
  • This month’s total time

From a UX perspective, some ideas:

  • A command like:
  • claude stats --session
  • claude stats --today
  • claude stats --week
  • claude stats --month
  • An optional end-of-day or end-of-session notification with a short summary
  • The feature could be opt-in for users who care about time tracking

I also have a name suggestion for the feature/branch/commit: /session-time.

Alternative Solutions

I’ve considered and tried a few alternatives:

  • Using external time tracking tools (e.g. Toggl, Clockify, OS-level screen time), but they are not directly tied to my activity inside Claude Code and require manual start/stop.
  • Manually writing down start/end times in a note or task manager, which is easy to forget and not very accurate.
  • Estimating time after the fact based on memory, which is often wrong and not reliable for billing or tracking progress.

These workarounds are either inaccurate, cumbersome, or completely disconnected from the actual development experience in Claude Code. A built-in solution would be much more seamless and valuable.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

Example scenario:

  1. I’m working as a freelance developer on a new feature for a client (for example, a new flow in a React frontend + some logic in a Node.js / backend service).
  2. I open Claude Code and start a coding session to implement the feature, going back and forth between files, refactoring code, and testing.
  3. Throughout the day, I might take breaks or switch tasks, but Claude Code continues tracking my active coding time.
  4. At the end of the day, Claude Code shows me a summary like:

“You’ve been coding for 3h 25m today (1h 40m on Project A, 1h 45m on Project B).”

  1. I can then:
  • Use that time to bill my client accurately
  • Compare this to previous days/weeks to see if my efficiency is improving
  • Better estimate future tasks for similar features

Another example:

  1. A beginner uses Claude Code while learning to code.
  2. Each week, they open a simple “time stats” view to see:
  • Total coding time this week
  • Total coding time this month
  1. Over time, they can see that they’re investing more consistent hours and track their progress in a concrete way, which is very motivating.

Additional Context

Additional context:

  • Suggested internal/branch/commit name: /session-time.
  • This feature is inspired by time tracking tools used by freelancers and productivity-focused developers, but having it built directly into Claude Code would make it much more accurate and convenient.
  • From a privacy perspective, this feature wouldn’t need to store detailed activity logs – only aggregate time per session/day/week/month.
  • It could also integrate nicely in the future with:
  • Project/workspace stats
  • Simple visual charts of coding time over days/weeks
  • Optional export of time data for invoicing or reporting

I’d be happy to provide feedback or test a beta version if this feature is considered.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗