The quickest answer
Run /usage inside Claude Code to see your remaining usage against the 5-hour window and the weekly cap, or open claude.ai/settings/usage in a browser for the same picture. Use /cost during a session to see the spend and token totals for that session specifically.
What /usage and /cost show
/usage reports where you stand against your plan limits — the short rolling window and the weekly allowance — so you can judge how much runway is left before a reset. /cost focuses on the current session: tokens consumed and the spend that maps to. They answer different questions: /usage is about runway, /cost is about this session.
Reading the two limits together
Claude Code enforces a rolling 5-hour window and a separate weekly cap that reset on different clocks. A common surprise is being fine on the 5-hour window but locked by the weekly cap, or the reverse. Checking /usage shows both at once so you know which limit is actually about to bite.
Why the terminal number is not your real bill
The in-terminal view is scoped to Claude Code. It does not include your Claude Pro or Max subscription, your ChatGPT Plus or Cursor plans, or your OpenAI and Gemini API spend. For most builders the subscriptions are the larger, easier-to-forget part of the monthly total, so the terminal number understates what you are actually paying for AI.
Keep the runway visible while you work
Running /usage works, but only when you remember to run it — usually after a session already feels tight. Tokens 4 Breakfast keeps the Claude Code window, weekly pressure, and your combined spend across providers in the macOS menu bar, so the number is in view during the session instead of after you are locked out. Free for one provider, about two minutes to set up.