How fast do your Claude Code agents run, and who is the session waiting on? Reads your local Claude Code logs, prints speed and time shares. Nothing leaves your machine. A developer released a Python script that parses local Claude Code session logs (~/.claude/projects/*/*.jsonl) to report how many responses ran in standard versus fast mode, the median end-to-end output speed in tokens per second, and the share of time spent by the model, tools and the human across sessions. The tool reads only timestamps, token counts and the speed field, never message content, and keeps all data on the local machine. It caps tool waits at 5 minutes and human gaps at 1 hour, and computes speed only on responses of 200 or more output tokens. | | /usr/bin/env python3 | | | """How fast do your Claude Code agents run, and who is the session waiting on? | | | Reads your local Claude Code session logs ~/.claude/projects/ / .jsonl and prints: | | | - how many responses ran at each speed setting standard vs fast mode | | | - the median end-to-end output speed of your responses, in tokens per second | | | - while the agent works on its own: the model's share of the time vs the tools' | | | - across whole sessions: the model's, the tools' and your own share of the clock | | | It reads only timestamps, token counts and the speed field. It never prints or | | | sends message content. Nothing leaves your machine. | | | Usage: | | | python3 claude code speed.py last 30 days, every project | | | python3 claude code speed.py 7 last 7 days | | | python3 claude code speed.py 30 ~/.claude/projects/