Free alpha · for Claude Code

Control your fleet of Claude terminals.

The instrument panel for developers running several Claude Code sessions in the terminal. Keep the CLI you already live in — Damask adds the glance you're missing: which session is blocked and why, what each is costing, how close to the context wall. Calm by default, local, no subscription.

Download for macOS See how it works

Free during the alpha · Apple Silicon · macOS 14+ · signed & notarized · transmits nothing about you or your code

The pile of tabs problem

Past one session, Claude Code becomes a guessing game.

The moment you're running three terminals of Claude, the terminal stops telling you what matters. Damask answers the four questions that pile up.

“

Which Claude needs me — and what for?

In a wall of tabs there's no signal. Damask shows a live status dot per session, fires a native notification and a Dock badge the moment a backgrounded session wants you, and — because it reads Claude Code's own hooks — puts the actual reason on the row: the permission it needs, the question it asked. You triage without opening every pane. Click to jump straight there.

“

What is all this costing?

A built-in usage view reads your local transcripts and estimates spend at list prices, with a daily budget alarm. Each session's panel shows today's cost for that directory — and one Settings toggle reads the official 5-hour and 7-day plan-limit percentages straight from Claude's own status line.

“

Is context about to run out?

Every session shows how full its context window is, so you see the wall coming instead of hitting it. One key hands the brief to a fresh session before compaction garbles a long run.

“

Can I get my fleet back tomorrow?

Sessions are restored across restarts and resume the exact conversation. Names come from the live terminal title, order is drag-reorderable, worktrees and per-directory scratch pads persist. Quit, relaunch, and everything is where you left it.

What's inside

The layer the terminal can't give you.

See who needs you, what you're spending, and where each session stands — without leaving the real terminal. Every session is a genuine claude process in its own PTY, kept alive in the background; nothing is forked, proxied, or reimplemented.

Awareness & attention

Live status dots driven by Claude Code hooks. A backgrounded session that needs you raises a native notification and a Dock badge — carrying the reason it's blocked. Idle chatter stays quiet; it only goes loud on a real ask. Click to focus.

working needs you done error

Cost, context & quota

A usage view built from your local transcripts — list-price estimates, no external tools — plus a daily budget alarm and every session's context fill. A status-line bridge makes the fill exact and adds the official 5h / 7d plan limits.

context 41%$1.20 today5h window 62%

Multi-session cockpit

Many live sessions in one window — only the active terminal on screen, the rest running in the background with App Nap blocked so they never throttle.

⌘1–⌘9⌃Tab cycledrag to reorder

Git-worktree isolation

Spawn a session on its own branch and worktree, per session or by default — auto-removed when it's clean on close. It even follows the shell's cwd via OSC 7.

per-session branchauto-cleanup
Two-way, not just a viewer

The Claude inside a session can drive the app.

An opt-in, vendored /damask skill installs to ~/.claude/skills/damask on your consent. From inside a turn, Claude can call back over a token-gated localhost endpoint to:

Preview a file it just wrote Push a notification Copy to clipboard Open a URL Check its own tokens & context Spawn a sibling session

Bounded by design: a per-pane token, a write-allowlist of opened paths, previews rendered script-free, and spawn behind a Settings toggle plus a per-spawn confirm.

# inside a Claude Code turn
/damask preview report.html
→ opened in a preview pane

/damask notify "build is green ✓"
→ native notification sent

/damask usage
→ context 41% · $1.20 today

/damask spawn --worktree feat/tests
→ awaiting your confirm…
Why it wins

Claude-native. Lightweight. Yours.

Not a replacement for the CLI you live in — the instrument panel on top of it. Here's what only Damask brings to sessions you're already running.

The hook

Awareness you feel

Background a Claude and trust it'll ping you — with the reason attached: the permission it needs, the question it asked. Calm by default, loud only on a real ask. No wall of alerts, no guessing which pane.

The whitespace

The cockpit no one else has

Per-session cost, context fill, and the official 5h / 7d plan limits — at a glance across every session you're running. One place they all live together.

Additive

Adds to the CLI you use

Not a chat GUI you migrate to — the real claude in a real terminal, with the instrument panel layered on top. Keep your workflow; gain the glance. Per-session git worktrees keep parallel agents from colliding.

Closes the loop

A surface Claude can drive

Preview the artifact it just built, alert you, check its own spend — something a stack of terminal tabs simply can't offer.

Yours

Private, local, no subscription

It reads your machine and transmits nothing about you or your code — status hooks install on your consent, into a git-ignored project file. A one-time price when it ships: no cloud, no seat, no meter.

The wall

Never hit the context wall blind

A context meter on every session shows the wall coming. One key hands the brief to a fresh session before compaction garbles a long run — the handoff everyone else reinvents by hand.

Built for

Developers who've outgrown one session.

Parallel feature work

One Claude per feature, each on its own worktree, no stepping on each other.

Long-task babysitting

Kick off a refactor, switch away, get pinged when it's done or stuck.

Multi-project days

Flip between repos all day without losing track of a single session.

Budget discipline

Watch daily spend and get an alarm the moment it crosses your cap.

The Damask app icon
Download

Get the free alpha.

One signed, notarized DMG. Drag it to Applications and you're running. It keeps itself up to date from there.

Download Damask

The signed build is landing shortly — the link goes live the moment it's published. Want a ping when it's ready? Email us.

Apple Silicon — M1 or later. There is no Intel build.
macOS 14 (Sonoma) or newer.
Claude Code installed — the claude CLI. Damask runs your real sessions.
Signed & notarized — opens with a double-click. No “unidentified developer.”
Honest about the alpha. It's free and still evolving — expect the occasional rough edge and frequent updates (it updates itself). It's an Apple-Silicon Mac app only; there's no Intel, Windows, or Linux build, so please don't install it expecting one. It reads your machine and transmits nothing about you or your code. Hit a bug or want something? Email matthew@zyxt.com — we read everything.