Baaz

A native macOS window around Muse Code.

The muse CLI ships a terminal UI. This is the same agent with a real
window around it — approvals, questions, plans, todos and tool output drawn
as interface rather than printed as text.

What it does

• Chat over Muse Code. Drives muse serve as a child process and speaks
  MSP (JSON-RPC 2.0 as NDJSON over stdio); signs in the way the CLI does —
  a Meta account, or an API key.
• A streaming transcript with markdown, reasoning and tool calls folded
  into readable cards, per-turn token counts, a context meter with
  compaction, and a queue strip for steering a turn that is already running.
• Approvals, questions and errors as real UI — multi-stage approval
  cards carrying the server's own choices, question cards with previews and
  a timeout, error banners with retry.
• Projects. One window over several workspaces at once, grouped by
  project or by date, with per-project pinning, colour, and
  model/effort/approval defaults.
• Sessions: resume, rename, fork, archive. A draft — text, images,
  files — kept per project, and full-text search across transcripts.
• A composer with model, effort and mode menus, @-mentions,
  /-commands (including skills from muse skills list), prompt history
  and image attachments.
• Billing-tier awareness. Baaz probes which plan a login is on and warns
  before a turn would bill pay-as-you-go, rather than after the fact. See
  Cost.
• Light and dark themes, a command palette, and a keyboard-first keymap.

A walk through it

1. Sign in

Two ways in, and they bill differently: a Meta account draws on your Muse
subscription, an API key bills usage to that key. Baaz signs in over the
wire — the same account/* calls the CLI makes — and never keeps the
credential itself. That stays Muse's, in ~/.config/muse/auth.json.

2. Start a