u/Fluffy_Pear5455

Image 1 —
Image 2 —

I got annoyed at constantly opening different usage/rate-limit screens just to see if I was about to run into a wall, so I made a little local macOS widget for it.

It sits on my desktop/menu bar and shows Claude + Codex side by side:

  • 5h and weekly usage meters
  • reset countdowns
  • projected “you’ll hit the limit around X” based on current burn
  • compact/expanded modes
  • a local session diary so it can learn my usage/burn patterns over time
  • always-on-top toggle
  • quiet mode so it only bugs me when things are actually getting tight

It’s all local. No backend, no account scraping service. It just reads the local usage/rate-limit data the tools already expose and stores history on my machine.

Mostly built it because I kept breaking flow to check limits manually, and that felt dumb.

Thinking of adding more stuff too: latency tracking, session efficiency, better usage forecasting, maybe even “today is probably going to drain faster” hints based on trends, plus a status watcher for when Claude/Codex/OpenAI/Anthropic are having issues.

Small side project, but honestly it’s already useful.

u/Fluffy_Pear5455 — 9 days ago

Claude swarm on the left, Codex subagents on the right. same PR. same codebase. both are maxed out. both are thinking. both are spawning children.

Codex keeps naming its agents after dead physicists. claude is too serious with the names like d4-range-planner. very different vibes.

but honestly... having two completely independent AI labs collaborate on my feature branch and cross-check each other's work without knowing the other exists is LK the funniest and most unhinged shit i've stumbled into.

people talk about vibe coding... this is just vibes. if I wasn't reviewing code before this, idek what do i say now.. I don't even know wtf they are saying anymore ... But im loving it

u/Fluffy_Pear5455 — 14 days ago