AI usage not showing on Mac? A troubleshooting checklist

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

AI workflow illustration; example interface

First identify what is missing

An empty token total, a missing reset countdown and an absent agent session are different problems. Write down the provider, the label you expected to see and whether the value is blank, zero or simply old. Do not treat a blank limit as unlimited capacity, or a zero local total as proof that your account has no activity. This guide concerns MacStick’s local coding-tool integrations, not browser chat history or a provider billing outage.

Confirm where the session ran

Check that the work ran in Claude Code, Codex or Gemini CLI on this Mac and under the same macOS user account as MacStick. A session running over SSH on a remote server creates its history there. Work on another laptop, in a cloud environment or only in a provider’s website may not be present in local records. The MacStick browser demo never reads your Mac and always uses sample values. Moving a panel between screens does not change the source of its usage data.

Check the monitor and try a small local task

Open Settings → Monitors and confirm the relevant usage display is enabled. Run a normal small task in the local coding tool, let it finish, and allow the dashboard to refresh. Keep the original session open so you can identify it. If the coding tool itself fails or has not saved usage history, the monitor cannot manufacture that information. Avoid deleting session files as a troubleshooting shortcut: removing the history can remove the evidence needed to understand a missing total.

Separate missing history from different totals

Compare the same provider, model, date range and scope. One session and an entire day are different measurements. Running totals in a log cannot safely be added line by line; cached input can also have a distinct meaning. A tool update may change its record format, and an unknown model may lack a known price. Record the tool and MacStick versions when a problem begins after an update. The tokens, cost and limits guide explains these accounting differences.

If Claude limits or estimated costs are missing

Local Claude Code token history does not by itself establish remaining account allowance. For supported usage-window data, inspect the optional Connect integration in Settings → Monitors. A cost estimate depends on available token categories and the model-rate table; it is not your subscription invoice. Check Claude’s own account information when capacity or charges matter. For the source boundaries and setup, read Claude Code usage on Mac.

If Codex resets or Gemini allowances are missing

Codex limit windows can only be displayed when the available records contain the relevant information; a recorded value may also be stale. A local token count cannot reconstruct a missing window. Gemini CLI tracking in MacStick is token-only: a Gemini cost estimate or reset allowance is not a missing setting. See the Codex guide or Gemini CLI guide to check what that integration supports before trying to repair it.

If an agent looks busy when it needs a response

Usage and agent status follow different signals. A permission prompt inside a tool call can still appear as working. Check the original terminal or agent interface rather than assuming the dashboard is a permission-approval surface. MacStick does not approve tool calls or answer questions on your behalf. The agent-status guide explains the supported states and limitations.

Send a useful, private support report

If the issue persists, send support the macOS version, MacStick version, coding-tool version, affected provider, approximate time and a short sequence that reproduces it. Explain what you expected and what appeared. Start with a cropped screenshot of the relevant reading. Do not send API keys, authorization tokens or entire session logs: they may contain prompts, source code and private paths. If a small record sample is needed, redact it before sharing. Keep your provider’s own interface available as a fallback while the problem is investigated.

See the idea in action.

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

Try MacStick →