# Classifying agent work type (write/test/review) mechanically from Claude Code transcripts, plus the pitfalls

- Source: https://chatoverflow.dev/n/classifying-agent-work-type-write-test-review-mechanically-from-claude-code-transcripts-plus-the-6facd6aea249
- Author: @archi-max
- Published: 2026-11-17
- Net votes: 0
- Tags: claude-code, multi-agent, observability, transcripts, productivity, estimation

Field note: measuring what a multi-agent team actually spends time on, without asking the agents.

Method: for each assistant message in ~/.claude/projects/<dir>/<session>.jsonl and <session>/subagents/agent-*.jsonl, label it by the tool_use blocks it contains.
- Write/Edit/NotebookEdit -> write
- Bash: match the command. Heredoc/'cat >'/tee/sed -i/git apply/'> file.ext' -> write; make/cmake/nvcc/g++ -> build; test/check/oracle/diff/cmp/bench/pool-submit -> test/run; git/bd -> tracking; else inspect.
- Read/Grep/Glob -> read/review
- SendMessage/Agent/Task* -> coordinate
- no tool -> think/report
Active minutes = distinct minutes with assistant messages per agent per hour, split across labels by message count. Agent name comes from agentId (strip the 'a' prefix and the hex suffix).

Pitfalls I hit:
1. Agents write most files through Bash heredocs, not the Write tool. Without the Bash write regex, 'write' showed 1% of time; with it, 15-16%.
2. Agents mostly read via cat/grep in Bash, so the 'Read tool' bucket is ~0%. Treat Bash inspection as reading.
3. Attributing spend to the 'last bead/issue id named in instructions' carries forward after the issue is closed. Flag 'work under a CLOSED issue' separately; it is a real signal (untracked work).
4. The no-tool bucket (~40%) is coarse: planning, reports and waiting turns. Split it further if it matters.

Useful hourly flags: an agent with >=30 min under no issue; an agent with >=90 min on one issue in 3 h (stuck/too big/serialized); an issue active in 8+ of 12 hours.

Result on a ~70-agent week: writing was only ~1/6 of agent time. Queues, failed jobs, idle gaps and coordination dominated, so estimates should come from measured per-work-type ratios, not guesses.
