token usage, billing, limits, privacy
Start here
Pick the usage, limit, cost, or data question you are trying to answer. Supported-reader pages explain the exact local data available; unsupported tools lead with their native source of truth.
How to check OpenClaw token usage
Pairs OpenClaw's native source of truth with a directly supported local aggregate workflow and clear privacy boundaries.
Direct local support
Why OpenClaw token usage gets high
Provides a symptom-to-cause decision tree and before-and-after measurement loop instead of a generic list of optimization tips.
Direct local support
Google Antigravity usage limits and tracking
Leads with Google's account view as the entitlement source of truth and clearly labels local presence detection as non-usage data.
Detection only
Kiro credits and usage limits
Separates native credit entitlement from model-token estimates and gives a concise checklist for investigating unexpected consumption.
Not parsed by whoburnedmore
Zed Agent token usage and cost
Routes readers to Zed's authoritative billing view and supplies an estimate framework without pretending unsupported data is available.
Not parsed by whoburnedmore
Roo Code usage and cost after shutdown
Treats Roo as a legacy product, distinguishes historical local records from current service, and provides a practical migration checklist.
Legacy local records only
Export AI coding usage to JSON or CSV
Provides copyable export commands, a field dictionary, validation checks, and a clear distinction between default sync and --local.
Supported sources only
Claude Code Usage Dashboard: What to Track
A good Claude Code dashboard is not just a total token counter. It shows cost, session pace, context pressure, and the projects that repeatedly burn the most.
published 2026-06-25
Claude Code Cost per Session: Measure It
Session cost is the unit developers understand: one debugging run, one feature build, one refactor, one billable chunk of AI work.
published 2026-06-27
Claude Code 5-Hour Window, Explained
The 5-hour window is a rolling usage window. The practical question is not when the day resets, but whether your current burn rate will outrun the quota.
published 2026-06-29
Claude Code Weekly Limit: Plan Heavy Work
Weekly limits punish unplanned bursts. The fix is not to use Claude Code less, but to reserve high-burn work for the moments when it has the most leverage.
published 2026-07-01
Is Claude Code Max Worth It for Coding?
The Max question is not just price. It is whether higher usage capacity prevents expensive interruptions often enough to justify the plan.
published 2026-07-03
Claude Code vs Cursor Cost: Real Tradeoffs
Claude Code and Cursor feel different because one is terminal-first and the other is IDE-first. Cost comparison has to follow the workflow, not just the sticker price.
published 2026-07-05
Codex Local vs Cloud Cost: What Changes
Local and cloud Codex work can share plan limits, but they feel different because cloud tasks are often larger, asynchronous, and harder to stop mid-loop.
published 2026-07-07
Codex Plus vs Pro Limits: Upgrade Logic
A higher Codex limit is valuable only if it protects valuable work. The decision should come from measured usage, not anxiety after one blocked session.
published 2026-07-09
Codex Weekly Limit Reset: How to Plan
The reset question matters because Codex work often clusters around deadlines. A visible weekly burn chart gives you a safer plan than waiting for an error.
published 2026-07-11
Codex Usage-Based Pricing: Budget Guide
Usage-based pricing changes the question from what the tool costs to what each delegated task is worth.
published 2026-07-13
GitHub Copilot AI Credits, Explained
GitHub's move toward AI Credits makes Copilot feel more like a usage budget than a simple flat subscription.
published 2026-07-15
Copilot Premium Requests vs AI Credits
Premium requests and AI Credits are both attempts to express scarce model capacity, but they create different mental models for developers.
published 2026-07-17
GitHub Copilot Enterprise Usage Billing
Enterprise Copilot billing is not just a finance issue. It affects developer behavior, admin controls, and how teams evaluate AI coding ROI.
published 2026-07-19
Cursor Usage Dashboard: What It Should Show
Cursor usage visibility is most useful when it tells you which work pattern caused cost pressure, not just whether a monthly limit is close.
published 2026-07-21
Cursor Agent Mode Cost: Reduce Runaway Loops
Agent Mode cost is usually a loop problem: too much context, too little feedback, or a task that was never made small enough.
published 2026-07-23
Cursor Team Spend Controls for AI Coding
Spend controls work when they guide behavior early. They fail when they only appear after a surprising invoice.
published 2026-07-25
Cursor vs Copilot Cost: Team Comparison
Cursor and Copilot overlap, but they are not interchangeable. Cost depends on how much work happens in the IDE, GitHub, chat, review, and agents.
published 2026-07-27
Windsurf Credits vs Quotas: Cost Meaning
Credits and quotas are two ways to communicate limited AI capacity. The operational problem is the same: developers need to know what work consumes the budget.
published 2026-07-29
Windsurf Cascade Usage Cost: Track It
Cascade cost control is mostly workflow control. The more precise the task, the easier it is to keep agent usage productive.
published 2026-07-31
Windsurf Team Usage Limits: Admin Playbook
Team usage limits should create visibility, not fear. Developers need to know what is normal and when to ask before a large agent run.
published 2026-08-02
Replit Agent Credits: Budget Your Builds
Replit Agent credits are easiest to manage when each build is treated as a project budget, not a casual chat allowance.
published 2026-08-04
Replit Core vs Pro Agent Cost
The Core vs Pro decision depends on how many people build, how often Agent work runs, and whether credit rollover or team controls matter.
published 2026-08-06
Lovable Build Credits: What Burns Them
Lovable credits are consumed by build and AI feature workflows, so teams should budget by feature scope rather than by prompt count.
published 2026-08-08
Lovable AI Gateway Usage: Avoid Surprises
The builder that creates your app and the AI calls inside your app can produce different bills. Treat production AI usage like a product meter.
published 2026-08-10
Devin ACU Cost: Understand Agent Compute
Devin's ACU framing measures agent compute rather than simple messages. That makes task scoping and outcome review especially important.
published 2026-08-12
Devin vs Claude Code Cost: Autonomy vs Control
Devin buys more autonomy. Claude Code buys tighter interactive control. The cheaper tool depends on the task, not the brand.
published 2026-08-14
Vibe Coding Tool Cost Comparison 2026
Vibe coding tools charge in different units: seats, credits, messages, ACUs, and tokens. Convert them back to task cost before choosing.
published 2026-08-16
AI Agent Credit Systems, Explained
Credits exist because agent work has uneven compute cost. Your job is to translate credits back into understandable engineering work.
published 2026-08-18
AI Token Budget Template for Developers
A useful AI token budget is small enough to follow weekly and specific enough to catch waste before the invoice arrives.
published 2026-08-20
AI Coding Team Spend Policy Template
A good spend policy tells developers when to use AI more, when to slow down, and how to explain unusually high burn.
published 2026-08-22
AI Coding ROI Metrics Beyond Token Burn
Token burn is an input metric. ROI needs output metrics: shipped code, faster reviews, fewer incidents, and developer time saved.
published 2026-08-24
Tokenmaxxing vs Productivity: Use the Metric
Tokenmaxxing is useful when it reveals adoption and experimentation. It is harmful when high consumption becomes the goal.
published 2026-08-25
AI Token Leaderboard for Teams: Safe Setup
A team leaderboard should create shared awareness, not surveillance. The safest version is opt-in, aggregate-first, and paired with outcomes.
published 2026-08-25
AI Sprawl Cost Control for Engineering Teams
AI sprawl happens when every developer adopts tools faster than the organization can see cost, risk, and duplicated workflows.
published 2026-08-25
Model Context Window Cost in AI Coding
Context is not free. The more a coding agent must read and remember, the more token pressure the session creates.
published 2026-08-25
Prompt Length Token Cost: Coding Agent Guide
Prompt length matters because coding agents often resend context, logs, and instructions across a session.
published 2026-08-25
Local AI Coding Logs Privacy: What to Share
Usage tracking should not require sending source code or prompts. The safest trackers collect aggregate burn, dates, tool names, and optional public handles.
published 2026-08-25
Open Source AI Usage Tracker: What Matters
Open source matters most when the tracker reads local developer data. You should be able to inspect what is collected and how it is sent.
published 2026-08-25
Best Claude Code Monitor Alternatives
The right Claude Code monitor depends on whether you want a menu bar, a CLI report, a cross-tool dashboard, or a public leaderboard.
published 2026-08-25
SessionWatcher Alternative for Terminal Users
SessionWatcher is built around a native monitoring experience. Terminal-first users may prefer a CLI that runs inside their existing workflow.
published 2026-08-25
How to Check Claude Code Token Usage
See your Claude Code tokens by day, model, and project — and how the built-in /usage compares.
How to Check Codex CLI Usage and Token Cost
Codex CLI's /status only shows the current window — here's how to see your full history and cost.
How to Check Gemini CLI Usage and Cost
The token-spend view Gemini CLI is missing — surfaced from the logs it already keeps.
How to Check GitHub Copilot Premium Request Usage
Premium requests run out fast — track them alongside your other AI coding spend.
How to Check Cursor Usage and Token Cost
Cursor's dashboard stops at Cursor — see it next to every CLI agent you run.
How to Check opencode Token Usage and Cost
opencode keeps detailed logs — here's how to turn them into a token + cost total.
How to Check Amp, Droid, and Goose Token Usage
The newer agents don't have usage dashboards yet — one command covers all three.
How to Check Kimi CLI Usage and Cost
Kimi CLI shows the live run but no history — see your full token spend with one command.
How to Check Qwen Code Usage and Limits
Qwen Code's free quota is small — see exactly how many tokens you've used before you hit it.
How to Check Kilo Code Usage and Cost
Kilo Code shows per-task cost only — get the running total across days, tools, and models.
How to Check Hermes Agent Token Usage and Cost
Hermes spans 300+ models, so spend scatters — consolidate it into one daily breakdown.
How to Check Pi Agent Usage and Cost
The Pi agent has no spend surface — turn its logs into a daily token and cost total.
How to Check Codebuff Usage and Cost
Codebuff fans out across sub-agents — see the whole multi-agent token spend in one place.
How to Check Cline Usage and Cost
Read Cline's live meter, then use its local history for a cross-agent daily and model rollup.
How to Check Aider Token Usage and Cost
Aider's cost is per-message — total it over time and track your terminal agents as one.
How to Check Windsurf Credits and Cost
Windsurf's credits hide real cost — read the meter, then see token spend for your CLI agents.
How to Check Warp AI Usage and Cost
Warp meters AI requests by tier — check the meter, then track your agents' real token spend.
How to Check Amazon Q Developer Usage and Limits
Amazon Q caps agentic requests monthly — see your usage and your CLI agents in one view.
How to Check Trae Usage and Limits
Trae meters fast vs slow requests — read both quotas, then track real token spend cross-tool.
How to Check OpenHands Token Usage and Cost
OpenHands burns spend on long autonomous runs — read its usage, then total your CLI agents.
How Much Does Claude Code Cost Per Month?
Stop guessing from averages — measure your own monthly Claude Code cost from real usage.
How to Reduce Claude Code Token Usage
Ten ways to burn fewer tokens — starting with measuring where they actually go.
OpenAI Codex CLI Cost: Estimate and Track It
The token math behind Codex CLI pricing — plus how to track what you really spend.
AI Coding Cost: Claude Code vs Codex vs Gemini
A real cost comparison of the big three — measured from your logs, not marketing.
A Free Claude Code Cost Tracker
Track Claude Code cost over time—offline with --local, or submit aggregates to a shareable profile.
GitHub Copilot's 2026 Credit Billing, Explained
Copilot's June-2026 switch to credit billing — what it costs now and how to track it.
OpenAI Codex Credit Billing in 2026, Explained
How Codex's 2026 credit billing maps to tokens — and how to track what you actually spend.
Claude Code Usage Limit Reached? Here's What to Do
Locked out mid-session? See what you used and when the limit resets.
Claude Code Rate Limits, Explained
The weekly and 5-hour caps demystified — plus how to see your real utilization.
Codex Usage Limits: 5-Hour and Weekly Caps
Where to check Codex's 5-hour and weekly limits—and what local token history cannot tell you.
Why Your Claude Code Context Window Fills Up
What eats your context window — and how token totals reveal it.
A ccusage Alternative With a Leaderboard
Built on the same data as ccusage — with a cross-tool dashboard and a leaderboard on top.
ccusage vs tokscale vs whoburnedmore
A neutral feature-by-feature table of the three main token trackers.
The Best AI Coding Token Trackers in 2026
ccusage vs tokscale vs native dashboards vs whoburnedmore — a free, cross-tool comparison.