Beta — 2,400+ Claude users

The interface Claude should have shipped with.

Real-time cost and session intelligence for Claude Code. See spend, context health, burn rate, and recent session history without sending your data anywhere.

Join waitlist See it in action →
✓ Local-only. No backend. ✓ macOS menu bar app + CLI/TUI ✓ Reads ~/.claude/ locally
2,400+
Beta users
$340
Avg. monthly savings
100%
Processed locally
4.9★
Average rating
The problem

Claude Code is powerful.
Its session state is mostly hidden.

Claux exists to make cost, context, and session history visible while you work.

Critical
Invisible Session State
Cost, context health, cache behavior, and session pacing are hard to see while Claude Code is running.
High
Unpredictable Costs
A long agentic session can quietly compound cost before you notice the burn rate.
High
Context Degradation
When context fills up, output quality drops. Claude Code does not make that trend obvious enough.
High
No Spend Pacing
Without today, week, and month rollups, it is hard to stay inside a budget while you work.
Medium
No Session History View
You need recent sessions, models, and project breakdowns to explain where your spend actually went.
Critical
Poor Local Tooling
Most dashboards want your session data on someone else’s server. That is a bad trade for professional work.
Product preview

Your Claude sessions,
finally legible.

Core product

Two surfaces. One local source of truth.

Observe

The flight instruments Claude never shipped.

Claude Code gives you outputs. Claux gives you instrumentation. Track live session cost, token usage, context health, cache behavior, burn rate, and recent history in one place. The goal is simple: make it obvious what is happening right now, what it has cost so far, and whether the session is still healthy enough to keep running.

Menu bar

A native macOS menu bar app that stays out of the way.

The desktop app is built for ambient monitoring. It sits in the macOS menu bar, pulses when a session is active, and gives you a compact popover with the numbers that matter: active session cost, context health, burn rate, model, token breakdown, and spend summaries for today, this week, and this month. No browser tab. No separate backend. No data leaving your machine.

CLI / TUI

A terminal-first dashboard for people already in the shell.

If you live in the terminal, Claux stays there. The CLI gives you fast commands for active session status, spend summaries, recent sessions, analytics, exports, and tags. The TUI gives you a live overview screen without breaking flow in tmux, SSH, or local terminal work. Same local data source, same session model, different surface for a different workflow.

Getting started

From install to visibility in 3 steps.

Install Claux

Download the macOS app from the DMG, or build the CLI from source via the GitHub repository.

Download DMG ↓ GitHub source →
Read your local session logs

Claux reads your ~/.claude/ session logs locally. Your code never leaves your machine.

Choose your surface

Use the macOS menu bar popover for ambient monitoring, or run claux tui for a live terminal dashboard.

Pricing

Start free. Get early access to Pro.

Free forever
Free
$0
/ month
  • CLI commands for active session status
  • Live TUI dashboard
  • Spend summaries and recent sessions
  • Local JSON / CSV exports
  • Reads ~/.claude/ locally
  • macOS menu bar app
  • Advanced analytics and model breakdowns
  • Budget tracking and threshold alerts
  • Expanded session history and diagnostics
Download
Coming soon
Pro
$8
/ month
Early-access pricing for first adopters.
  • Everything in Free
  • Early-access builds — new features before they ship publicly
  • Full export suite — JSON, CSV, filtered by date, project, or model
  • Unlimited CLAUDE.md generation and AI-assisted optimization
  • Advanced session quality analytics — acceptance rates, rejection patterns, and agent outcome scoring
  • Intelligent context optimization — live guidance on when and how to reduce window pressure
Get early access
What people say

From beta users who actually get it.

"

I was spending heavily on Claude Code and had no idea which sessions were responsible. Claux made the pattern obvious in a day. Once I could see burn rate and session history in one place, cutting waste was straightforward.

Alex R.
Solo Founder
"

The menu bar app is the right surface for this product. I do not want another browser tab open all day. I want to glance up, see context health and cost, and get back to work.

Maya T.
Engineering Lead, Series A startup
"

The TUI is what sold me. I stay in tmux all day, and `claux tui` gives me live session state without breaking flow. It feels like the missing dashboard Claude Code should already have in the terminal.

Jordan K.
Senior Developer
"

The context health meter changed how I work. I used to restart sessions by feel. Now I can see when a conversation is getting full and cut over before quality drops hard.

Priya S.
Full-Stack Engineer
"

Recent sessions and model breakdowns answered the question we kept asking in standup: what exactly cost us money yesterday? Before Claux, we were guessing. Now we can point to the sessions and models directly.

Marcus D.
VP Engineering, 12-person team
"

The local-only architecture mattered to me more than the charts. I work on client code. I was not going to upload session metadata to a third-party service just to get visibility into my own usage.

Sam W.
Independent Consultant
"

Exports are underrated. I pull the JSON and CSV into my own reporting pipeline, but day to day I mostly just use the live view. That balance is exactly right.

Lee C.
AI Engineer
FAQ

Common questions.

This is a macOS Gatekeeper prompt that appears because Claux is not yet notarized through Apple's developer program. Your download is safe — here's how to open it:

1. Right-click (or Control-click) the DMG → Open
2. Click Open in the dialog that appears
3. Drag Claux.app to your Applications folder
4. Right-click Claux.app → Open → Open once more

After that first approval macOS remembers your choice and Claux opens normally. Alternatively, run xattr -cr ~/Downloads/Claux-1.15.1-release.dmg in Terminal before mounting the DMG.

No. Claux reads the local metadata that Claude Code writes to ~/.claude/ session logs: token counts, model names, timestamps, costs, and session identifiers. Your code, prompts, and responses stay on your machine.

Two product surfaces: a native macOS menu bar app for ambient monitoring and a CLI with a live TUI dashboard for terminal-first workflows. Both read the same local Claude Code session logs and focus on cost, context health, session history, and spend visibility.

Yes. If Claude Code writes the session logs locally, Claux can read them. That makes it useful across Claude Code setups where ~/.claude/ is the source of truth.

ccusage is great for checking usage quickly. Claux is broader observability: active session monitoring, context health, live TUI, recent sessions, spend rollups, exports, and a native macOS surface for always-on visibility.

By design. Claux is local-only. The product is built around reading your Claude Code session logs on your own machine and keeping that data there. The two supported interfaces are the macOS menu bar app and the CLI/TUI.

The macOS menu bar app is macOS only. The CLI and TUI are designed for terminal workflows and currently target macOS and Linux.

Yes. The CLI supports local JSON and CSV export so you can audit spend, build your own reports, or move the data into a spreadsheet pipeline.

Pro is the paid tier we are shaping around the native macOS app, expanded analytics, alerts, and richer diagnostics. Joining early access gets you into the first rollout waves and helps define which features should graduate first.

Stop guessing.
Start understanding.

Join 2,400+ Claude users who want local, real-time visibility into Claude Code sessions.

No spam. We’ll email invite waves and launch updates only.

Local-only · macOS menu bar app + CLI/TUI · Built for Claude Code