Teaching Claude about your codebase, once, for everyone
I’ve been building a CLI tool to monitor Claude Code usage: tokens consumed, costs per session, tool breakdown by volume. The cost numbers weren’t surprising. But the tool breakdown was. 1 2 3 4 5 6 7 Tools by volume (last 7 days, all projects) ------------------------------------------------ Bash ████████████████████ 427 (48%) Read █████████████ 270 (30%) Edit █████ 112 (13%) Write █ 30 ( 3%) Agent █ 16 ( 2%) 30% of all tool calls are Read operations. Not writing code, not running tests. Just Claude opening files to understand how the codebase is structured before it can help with anything. Context it builds up over the session and loses completely when the session ends. ...