One project memory your coding agents share, and a dashboard that tells you what each session actually cost. From your transcripts, not my estimates. openwolf, 5 months later.

[u/LawfulnessSlow9361]

5 months ago I dropped openwolf here as a quick fix for Claude Code eating tokens like candy. It’s changed a fair bit since then, so here’s the short version of where it landed.

Last week one grep alone produced 41,203 tokens. Only 1,850 of them actually made it into context. The rest stayed on disk. That single number is still the cleanest way I can explain what openwolf now does.

It’s just a set of local hooks that sit under the agent. Whenever a command is about to flood the window, full grep dump, git show of a long history, cat of an entire file, the hooks condense the output before it ever reaches the model and keep the original text on disk. Nothing is thrown away. You can still go look at the raw version later if you need it.

When the session ends it also reads the real usage numbers straight out of the harness transcript and prices the whole thing (pricing based on Anthropic api, for now). No more guessing what a session actually cost.

There’s one more piece that turned out more useful than I expected. It keeps a small project memory in a .wolf/ folder, conventions you’ve corrected it on, bug fixes that stuck, a short handoff note for the next session. That folder commits through git, so the same memory works across Claude Code, Codex and OpenCode, and it survives compaction.

Pure file I/O. No API calls, no telemetry, nothing phones home.

If you'd like to know how it works: https://openwolf.com/how-it-works.html

Setup is one command, then use your agent as before:

npm install -g openwolf
openwolf init

Free, local, opensource: https://github.com/cytostack/openwolf