Abandoned terminals
A Claude Code, Codex, or other agent session can sit waiting for your response for hours while you assume it's still working.
Loading dashboard…
Preparing live sessionsOperational control for Claude Code and Codex
Your agents keep working. You know exactly when to step in.
CloudUsage monitors sessions, limits, costs, and status across all your code agents in real time, from every machine you use. Works with Claude Code, Codex, and new providers without changing how you work.
Start for free
npm i -g cloud-usage-tokenFree · No credit card · Your code never leaves your machine.
Create your free account to generate the API key that links your machine.
No more babysitting terminalsLive sessionsMetadata only30-second install
The problem isn't running agents
The problem is losing track of them.
Claude Code, Codex, and other agents can keep moving while you focus on something else. But if you don't know which provider is active, which one is stuck, which one is asking a question, or which one is burning context, you end up flying blind.
Invisible limits
Context, tokens, and quotas move differently depending on the provider; if you can't see them, they interrupt your flow right when it hurts most.
Fuzzy costs
Multiple sessions, providers, and machines turn real usage into an unreliable mental estimate.
From black box to control center
Everything you need to know before switching back to the terminal.
Catch per-provider limits before they break your flow
Tokens, quotas, context windows, and estimated cost in real time, per session and per provider, without waiting for the agent to fail.
Know which agent is working, waiting, or blocked
Provider, status, project, branch, traffic-light signal, and context usage for every session in a single operational view.
Get alerted only when action is needed
We notify you when Claude Code, Codex, or another agent asks a question, sits idle, nears a limit, or runs something that deserves attention.
Keep your code out of the dashboard
CloudUsage syncs operational metadata. Your code, prompts, and transcripts stay on your machine.
How it actually works
A local agent watches. CloudUsage tells you.
The value isn't another pretty dashboard. It's turning scattered sessions from your code agents into operational signals: which provider is active, what's waiting, what's nearing a limit, and when you need to step in.
01
Install the CLICloudUsage becomes available as a global command.
02
Runs as a local serviceStarts in the background and watches sessions across Claude Code, Codex, and compatible providers.
03
Syncs secure signalsStatus, usage, context, project, and alerts travel to the dashboard.
04
You step in only when it mattersThe dashboard and notifications tell you exactly where to look.
Ready in 30 seconds
Install once. Control every session.
In under a minute you go from isolated CLIs to a local service that watches your agent sessions and publishes operational signals to your dashboard.
Step 01 · 10 seconds
Install the local agent
One global CLI, no new projects to create and no changes to your current workflow with Claude Code, Codex, or your active provider.
For people who actually delegate work
If your code agents are doing real work for you, you need real visibility.
CloudUsage is built for developers who've moved past treating agents as an experiment and now depend on Claude Code, Codex, and other providers to get real work done.
active
Solo devs
Let tasks run in Claude Code or Codex without staying glued to the terminal waiting for the next turn.
3sessions in progress
visible
Small teams
See which machines and providers have sessions active, blocked, or waiting for intervention.
4connected machines
measurable
Consultants
Understand usage, sessions, provider, and cost across projects without rebuilding it by hand.
Operational security
Visibility without taking your code.
CloudUsage is designed to observe operational signals from your agents, not the content of your work.
Code stays local
Your repo, files, and changes stay on your machine.
Metadata only
The dashboard receives status, provider, usage, estimated cost, and alerts.
API key access control
Each machine is explicitly linked with a key generated from your account.
We never send full prompts or full conversations to give you operational visibility.
Before and after
Without CloudUsage, you're flying blind.
Situation
Without CloudUsage
With CloudUsage
Session waiting for a response
You find out next time you check.
You get an actionable alert.
Context nearly full
You notice once the session loses momentum.
You see the warning light before it's too late.
Multiple machines and providers
Every CLI tells a different story.
One dashboard shows the real status per session and provider.
Usage and costs
Mental estimates per tool and late reviews.
Trend, consumption, and cost visible per provider.
Privacy
You depend on tools that may ask for more context than they need.
Operational metadata only; your code stays local.
Stop operating your agents blind.
Start for free in 30 seconds. No credit card. Your code stays private.
