Usage Meter CLI · in your terminal

Know exactly what your agent is spending, without leaving the terminal.

Just the numbers — a live token count and plan-limit fill, right in your terminal, for any AI coding agent in any IDE. Read-only, no Guardian: it reads the usage from logs on your own machine and shows it. Nothing more.

works with Claude Code, Cursor, Antigravity, Windsurf, Codex — from one install
Want it to also keep your agent alive across context resets? That's the full CLI with the Guardian — this Meter is the read-only usage view.
What it shows

A quiet gauge for your terminal.

Your live usage, read from logs on your own machine — so a long build never runs into a wall you didn't see coming.

Live token count

See exactly how many tokens you've used this session — the units of text an AI reads and writes, which is what you pay for.

Plan-limit fill

A percentage that shows how close you are to your plan's limit, so you can pace a long build instead of hitting a wall.

Any IDE, one install

Claude Code, Cursor, Antigravity, Windsurf, Codex — install it once on your Mac and it reads whichever agent is open.

Read-only & private

It reads your local context meter only. It never writes, never injects, and never sees your code or your prompts.

One install, every IDE

It watches from the outside.

You don't install the meter inside each editor. You install it once, and it reads the usage of whatever agent is open — for one command or a live, refreshing view.

vibeguard-meter ───────────────────────────── model claude-sonnet tokens 142,380 plan fill ███████░░░ 71% ───────────────────────────── add --watch to refresh live

Just the numbers, read from your own logs.

Run it once for a quick reading, or add --watch for a meter that refreshes as you work — in a split pane next to your agent. It's the cheapest insurance against a runaway session landing on your bill, and because it only reads local logs, it never touches your code or handles a provider API key.

How you'd use it

Just the numbers, for whoever wants them.

Same read-only meter in your terminal — whether it's your first build or your team's fiftieth.

Vibe coder

You live in the terminal now that your AI writes the code. One command tells you your token count — the text the AI reads and writes, which is what you pay for — and how much of your limit is left. No dashboard to open.

Developer

Run vibeguard-meter --watch in a split pane and keep a live token + limit readout next to Claude Code, Cursor, Antigravity, Windsurf, or Codex. Read-only — it never touches your code or prompts.

Enterprise

A zero-write, local-only usage readout that drops into any engineer's terminal and any IDE — visibility across the team without handing out provider API keys.

Install & how it works

Up and running in under a minute.

A few quick steps in your terminal (every IDE has one built in). After that it runs for all your editors.

1 · Download & unzip

Get the .zip with the button and double-click it to unzip the vibeguard-cli folder. Needs Python 3.8+.

2 · Install it

In Terminal, run pipx install vibeguard-meter (or pip install . from the folder).

3 · Read your usage

Run vibeguard-meter for a one-shot reading, or vibeguard-meter --watch for a live meter.

The commands
pipx install vibeguard-meter # install once vibeguard-meter # one-shot usage reading vibeguard-meter --watch # live, refreshes every few seconds

Ready to see your usage?

Download the Meter CLI and run vibeguard-meter. Included with your Vibe Guard subscription. Want the Guardian too? Get the full CLI.