aide spends its life doing things you can't see: injecting memories and decisions at session start, answering the assistant's MCP queries, deciding which skill to surface. Useful, but invisible, and invisible machinery is hard to trust or tune. So aide grew a web dashboard, aide-web, to make it observable.
The centre of it is token intelligence. Every context aide injects and every fact it serves has a cost and, ideally, a saving: the decision it handed over is tokens you didn't spend re-explaining your auth strategy; the precise code-index answer is the wad of source you didn't have to paste in. The dashboard tracks both sides, spent versus avoided, per tool and over time, so "is this actually helping?" stops being a vibe and starts being a chart.
aide dashboard launches the web UI; aide status gives you the same picture in the terminal if you'd rather not leave it.
One honest caveat, and it's why the feature is labelled experimental: the token counts are estimates. They come from calibrated per-language character ratios, not a real tokeniser, so they're good for relative comparison and spotting trends, not for exact cost accounting. Treat the shape of the graph as the signal, not the third decimal place. Repo and docs on GitHub.