Original Summary

I built this: TokenCensus ( https://github.com/rodriveiga01/tokencensus ). Two reasons. One boring, one deeply unserious. The boring one: my coding agents were burning tokens across Claude Code, Codex, Opencode, Cline and Hermes, and I had no single number. Now I do: - menu-bar counter + dashboard - per-tool, per-model, per-repo splits - one SQLite file, zero network calls - the README's badges phone home more than the app does The unserious one: Tibo. Codex people know — sometimes your weekly window jumps back to 100% overnight and nobody can prove anything. Mine stamps every reset with before/after evidence: $ tok tibo Tibo did it again 🙏 — 3 reset(s) caught last: codex:weekly · 16/09/26, 02:13 (plus tok tibo-pack for manual reply-guys — no bots, I'm not getting banned for this) Honest limitations: - Opencode day-splits are approximate, no backfill, first week badged partial - gaps (locked DBs, revoked perms) show as badges, never silent zeros - macOS 14+ only · Swift · MIT Feedback I actually want: CSV export vs. per-repo weekly caps next — which would you use? And yes, Cursor people, I know you're going to ask. The answer is still no. 🙂   submitted by   /u/rodriveiga1000 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/18 08:09:10