Loombar CLI for macOS

Your agents.
One command.

See Claude, Cursor, and Codex while they work. Read honest usage, find local servers, and give scripts a stable JSON contract—all from the data already on your Mac.

Download for macOS ↘Read the docs →

$ loombar status --jsonlocal by default · no provider keys

loombar — zsh — 92×28local

~loombar status

Loombar snapshot

Usage day: 2026-08-10

● 3 agents working

Claude Refactor authentication opus-5 loombar-web

Cursor Polish the CLI docs auto website

Codex Fix sync retry logic gpt-5.6 cloud-sync

Usage 18.4M tokens Raw cost ~$14.82

Open 8 sessions Ports 3 projects

One local interface for

CClaude↗Cursor⌁Codex

More signals, without another telemetry agent.

01 Why Loombar CLI

The fastest way to ask your machine what your agents are doing.

Loombar reads provider-native sources instead of flattening different measurements into one suspicious number. Useful in your terminal, dependable in a script, and quiet when nothing needs attention.

02 Command reference

Five clear questions.
No configuration maze.

Human-readable by default. Add --json anywhere automation needs to take over.

What is happening?

loombar status

A complete local snapshot: working agents, usage, plan meters, and development ports.

loombar status↗

Who is working?

loombar agents

Live Claude, Cursor, and Codex activity with project, model, and working state.

loombar agents --json↗

What did it cost?

loombar usage

Billable local history and honest Cursor account totals for one calendar day.

loombar usage --day 2026-08-10↗

What is running?

loombar ports

Project-aware localhost discovery, with infrastructure hidden until you ask for it.

loombar ports --all↗

Is everything connected?

loombar doctor

Check provider data access, CLI availability, and the local tools Loombar relies on.

loombar doctor↗

Explore every option →

03 Designed for pipes

Readable for you.
Stable for your scripts.

Every JSON response includes a schema version, command name, and generated timestamp. Missing upstream data stays null—it never quietly becomes zero.

01 Versioned JSON envelope
02 Predictable exit codes
03 Exact token fidelity labels

agents.json

{
  "schema_version": 1,
  "command": "agents",
  "generated_at": "2026-08-10T08:05:35.817Z",
  "working": 3,
  "open": {
    "claude": 4,
    "cursor": 2,
    "codex": 2
  },
  "agents": [
    {
      "platform": "codex",
      "name": "Ship CLI docs",
      "status": "working",
      "model": "gpt-5.6"
    }
  ]
}

04 Local means local

It observes your tools.
It does not replace them.

Keep the subscriptions, credentials, and workflows you already use.

01 / Native sources

Reads the ledgers already on disk.

Claude and Codex usage comes from local billable history. No extra daemon and no duplicate event stream.

02 / Honest fidelity

Different providers stay different.

Cursor account tokens and context fill remain clearly labeled. If its API fails, Loombar does not invent a total.

03 / No new secrets

Uses the sign-ins you already trust.

Provider credentials stay with their provider CLIs. Loombar does not ask you to paste API keys into another product.

Ready when your terminal is

Know what is working
before the prompt finishes.

Free local monitoring. macOS 14+. Claude, Cursor, and Codex.

Download Loombar ↘Install the CLI →

Your agents.One command.