[FEATURE] \Time-usage

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 30, 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

Often I have long running sessions that not use a lot of tokens. less than 100k tokens can run for hours, and I want to know which parts can be optimised. Is Claude thinking 20 minutes? Does my tests take 40 minutes? Maybe the compilation is burning time or that temporary script which claude created and deleted without me noticing.

Proposed Solution

I would like to have a command like /usage but for time and not token. Tell me how much time did my session take for: Generation / tool calls / Thinking / Background tasks / Idle and for tool calls I want a breakdown of which tool calls took the longest.

Alternative Solutions

I

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗