Gemini CLI token usage on Mac: a practical tracking guide

By MacStick · Updated 2026-11-15 · 3 min read

AI workflow illustration; example interface

Start with the question you need to answer

If you use Gemini CLI alongside other coding tools, switching terminals just to inspect usage interrupts your work. A compact dashboard can help answer “what has this Mac recorded today?” It cannot automatically answer “what is my complete Google bill?” MacStick’s Gemini integration measures local recorded tokens. It does not calculate Gemini spending or display a Gemini reset allowance. Keep those boundaries in mind when comparing tools.

Check a session in Gemini CLI first

In Gemini CLI, /stats displays statistics for the current session. The /stats model view includes model-specific token and quota information. Use this as a useful check of the session you are actively running. MacStick aggregates available local history, so a daily total and one session’s total need not match. See the official Gemini CLI command reference for current command behavior.

Bring local history into MacStick

Install MacStick on the same macOS user account where you run Gemini CLI, then open Settings → Monitors and enable the relevant usage display. Run a normal Gemini CLI session and allow the dashboard time to refresh. The integration reads chat history beneath ~/.gemini/tmp/, including supported JSON and JSONL formats. It does not require you to paste an API key into MacStick. The website demo contains sample data and will never read these files.

Interpret the token categories

Input, cached input and output represent different parts of a request. In MacStick’s Gemini parsing, cached input is part of the reported input total; do not add it again as if it were entirely separate work. Recorded thought tokens are included with output. Compare the same date range and model when checking a session against the daily view. Repeated message records are deduplicated by identifier where available, rather than treated as independent requests.

When the dashboard is empty or looks too small

First confirm that you used Gemini CLI on this Mac, rather than only the Gemini website or a remote development machine. Check that your CLI has written supported local chat history and that MacStick runs as the same user. Deleted history cannot be reconstructed by the dashboard. A CLI update may also change the record format. Keep the relevant app versions when reporting a problem, and share a redacted example only if support needs one; session files can contain private prompts or code.

Use the total to compare your own workflows

Try comparing a small edit with a broad investigation over similar time periods. Record the model and task size before drawing conclusions about efficiency. An increase can reflect useful work, extra context or repeated attempts; it is not automatically waste. For account-level capacity and charges, use the provider’s own records. Read how tokens differ from costs and limits before combining numbers from several AI tools.

See the idea in action.

The browser preview uses sample data and does not access your Mac.

Try MacStick →