macOS terminal workspace

One Mac window for the founder running five products on Claude Code.

CmdBrief pins agents, tasks, terminals, diffs, and browser context to each product—so you always know what is working, blocked, or waiting for you.

v0.4.5Apple silicon · macOS 26+Local-first workspaceSubscription required · 14-day money-back guarantee
Recorded from the current build, not a mockup — one agent pausing for approval before it runs cargo test, another writing the docs next door.
Founder reality

Your day is not one coding session. It is five products at five different stages.

One product needs a build fix. Another needs launch copy. A campaign is ready to review while yesterday’s release is producing traffic data. CmdBrief gives each product a home and rolls up the work that needs you, so switching products does not mean rebuilding the operating context.

Product tour

Give every product a home, run the next job, and see what needs you.

01

Give every product a workspace

Group its repos, tasks, terminals, browser tools, and saved layouts in a setup that returns exactly as you left it.

02

Move the product forward

Build with Claude Code or Codex, work through launch tasks, and keep growth or traffic-review tools open beside the product context.

03

Focus on the next decision

Agent status, attention badges, tasks, and native notifications show which product can move as soon as you act.

Voice Agent

Talk to CmdBrief. Keep agent instructions precise.

Ask what is running, blocked, or waiting; start or resume any supported agent; and dictate the next instruction without navigating between panes.

Voice session · listening
  1. Ask about your portfolio

    Inspect agent status, workspaces, usage limits, approved terminal output, and project files.

  2. Speak naturally

    Use a language supported by the selected provider, choose the assistant’s reply language, and have instructions translated into technical English before they reach the agent.

  3. Stay in control

    Workspace reading is session-scoped, and every state-changing action waits for local confirmation.

OpenAI Realtime or xAI Grok · Your API key · Provider usage billed separately · Language availability and accuracy vary by provider.

Capabilities

Every capability, shown on the real surface.

Agent status, session resume, rate limits, a real terminal, every tool, and git state — all in one local window.

Agent status

Claude Code, Codex, Grok CLI, Kimi CLI, OpenCode, and Cursor CLI report what they are doing, per pane, per tab, per workspace. Attention rolls up so a blocked agent cannot disappear behind a tab.

  • Working, needs action, stopped, or failed — not guesswork
  • Needs-action covers question, plan ready, approval, and waiting
  • Completed and failed runs raise a native macOS notification

Workspaces

3 active agents
  • cmdbriefClaude Code · 3 panesWorking
  • cmdbrief_frontendCodex · 1 pane
  • cmdbrief_backendClaude Code · 2 panesWorking
  • scratchno agentStopped

Status comes from three layered signals: agent hooks (Claude Code, Codex, Grok, Kimi, and Cursor CLI; authoritative, append-only JSONL), process liveness, and a screen-scrape fallback (how OpenCode is tracked).

Resume sessions

Your recent local agent sessions from every supported CLI, listed with the context you need to recognise them, and reopened in one click.

  • See title, working directory, and git branch; filter the list by provider
  • Reopens the exact thread with claude --resume or codex resume
  • Reads session metadata plus short, bounded previews — never full transcripts

Resume sessions

local only
SessionBranchTokensRuntime
Extend the pane position picker to dock panes beside specific panesmain128.4k22m
Stop forwarding keyboard-activated clicks to mouse-tracking TUIsmain86.1k14m
Add a hover scrubber with value and time callout to panel chartsmain201.7k41m
Clean a Rust target folder straight from the disk analyzermain63.9k9m

Reopens with claude --resume or codex resume. CmdBrief reads session metadata plus short, bounded prompt and response previews — never full transcripts.

Agent rate limits

The usage windows each provider actually reports, side by side, so you can decide where limited agent capacity does the most good.

  • Claude Code and Codex 5-hour and weekly windows, Grok CLI weekly credits, OpenCode Go rolling, weekly, and monthly windows, Cursor CLI monthly Cursor-models and Other-models pools
  • Countdowns to reset, with rollover detected once a reset passes
  • Toggle any window between remaining and used

Agent rate limits

remaining
  • Claude Code
  • Codex
  • Grok CLI
  • OpenCode
  • Cursor CLI

Windows are whatever each provider actually reports — 5-hour and weekly for Claude Code and Codex, weekly credits for Grok CLI, rolling plus weekly and monthly for OpenCode Go, monthly Cursor-models and Other-models pools for Cursor CLI. Kimi CLI exposes no usage data, so it shows none. Toggle between Remaining and Used; rollover is detected once a reset passes.

A real terminal underneath

Not a chat box with a shell bolted on. A hand-written xterm-class VT emulator on a GPU cell renderer, with every command annotated as it runs.

  • 256-colour and truecolour, alt-screen, bracketed paste, OSC 8 links
  • Command blocks record cwd, duration, exit status, and git state
  • Scrollback persists per pane and survives a restart

Command block

zsh
~/src/products/hiveCTLmain +2 −0
cargo test -p cmdbrief-core
running 214 tests test result: ok. 214 passed; 0 failed
exit 04.8s11 files dirty

Every command is annotated with its working directory, duration, exit status, and a git snapshot taken when it ran.

Every tool for a product, in one window

A workspace per product, tabs inside it, and a recursive pane tree you can split, drag, zoom, and restore exactly as you left it.

  • Terminal, file explorer, file viewer, git diff, browser, disk analyzer
  • Five layout presets, or split it yourself with weighted dividers
  • Workflows save a whole tab-and-pane setup and replay it

Layout presets

per tab
Single
2-col
2-row
3-col
2×2
TerminalFile explorerFile viewerGit diffBrowserDisk analyzer

Panes split recursively with weighted dividers, snap guides, and drag-and-drop rearrangement. Esc restores a zoomed pane.

Git state beside the agent that changed it

A per-repo dashboard and a dedicated diff pane, both entirely local. CmdBrief never pushes, fetches, or phones home.

  • Branch, upstream, ahead/behind, staged, unstaged, untracked, ±lines
  • Last 30 commits with diff previews and remote compare links
  • A read-only diff pane, syntax-coloured and size-capped

Git dashboard

local-only view
hiveCTLmain → origin/main · ahead 2, behind 0
11unstaged
1untracked
+248 −96lines
crates/cmdbrief-core/src/goals.rs
crates/cmdbrief-app/src/app/sidebar_ui.rs
crates/cmdbrief-app/src/app/chrome.rs
design/goals-overlay-plan.md

Branch, upstream, ahead/behind, staged, unstaged, untracked and ±lines, plus the last 30 commits with diff previews. No network calls.

01 / Portfolio
One window

Every product, project, and agent stays visible.

02 / Privacy
Local-first

Repos and workspace state stay on your Mac; connected services remain explicit.

03 / Continuity
Build → grow

One persistent context through every product stage.

04 / Leverage
One click

Turn the next action into a running agent.

Product context

The work around the product stays with the product.

Building, launching, marketing, and reviewing results use different tools. CmdBrief keeps the repo, files, local services, browser context, tasks, and agent runs organized around the product they serve.

  • Git diffs and repository health stay beside the product and agent that changed the code
  • Files, local web apps, campaign tools, and analytics dashboards can stay open in workspace panes
  • Cmd-click any URL in terminal output to open it in a browser pane beside the terminal that printed it
  • Repo-native and SKILL.md actions turn repeatable product work into reusable commands
  • Native notifications, in-app attention badges, and menu-bar system stats keep the portfolio visible from macOS
Recorded from the current build, not a mockup — Codex writing the docs while the working diff fills in beside it.
Native foundation

A founder control room with a serious terminal underneath.

CmdBrief stands on fast terminal fundamentals: GPU rendering, durable scrollback, split panes, command blocks, and git-aware context.

The control room
  1. A repeatable setup for every product

    Save tabs, panes, layout, and startup commands as a workspace you can reopen for any product. Secrets stay out of the file as ${NAME} references.

    layout.yaml
  2. MCP server mode

    CmdBrief is itself an MCP server. Your agent can inspect and reconfigure workspaces — every change staged and applied only after you approve it in-app.

    --cmdbrief-mcp
  3. The next action stays visible

    Per-workspace tasks carry status, priority, and acceptance criteria. Assign the next job to yourself, Claude, or Codex without detaching it from the product.

    status · priority
  4. Menu-bar monitor

    A native macOS menu-bar readout with live CPU, GPU, RAM, and battery. Agent attention surfaces as in-app badges and native notifications.

    NSStatusBar
  5. Safe imports

    Imported layouts have auto-run commands demoted to manual, so a shared workspace can never silently execute anything.

    auto-run demoted
The terminal underneath
  1. Split-pane layouts

    Weighted splits with snap guides, pane zoom, drag-and-drop rearrangement, and layout presets from single pane to 2×2.

    2×2 presets
  2. Git-aware panes

    Each command block records the git snapshot it ran against. The dashboard is a local-only view — it never pushes, fetches, or phones home.

    git snapshot
  3. Built for speed

    A Rust core with a WGPU renderer whose glyph pipeline is matched to the UI, plus a native Swift menu-bar layer. Fast under load, easy on the battery.

    WGPU
Founder workflows

One workspace for every stage the founder still owns.

The tools change at each stage. CmdBrief keeps the product, evidence, tasks, and agent work connected from build through review.

Explore founder use cases
  1. Build

    Build the next product

    Keep the repo, local app, implementation tasks, coding agents, and review evidence together from first commit through a working release.

  2. Launch

    Ship without losing the launch

    Keep release checks, launch tasks, browser previews, copy changes, and agent follow-ups attached to the product that is going live.

  3. Market

    Turn marketing work into execution

    Track campaign and content tasks beside the files, browser tools, and agent sessions doing the work instead of rebuilding context in every app.

  4. Review

    Review traffic with product context

    Open the analytics or traffic dashboard you already use beside the relevant workspace, launch notes, tasks, and agent follow-ups.

Across every stage
  • Delegate tasks, not context

    Write the job once, attach its acceptance criteria, and launch Claude or Codex with the product context already connected.

  • Run the portfolio solo

    Give every product a named, color-coded workspace and see which one is moving, blocked, or waiting for you before opening a pane.

Without CmdBrief

Products spread across terminals, browsers, notes, and dashboards

Coding in one context and launching in another

An agent waiting while you work on a different product

Rebuilding context every time you switch products

Guessing which product needs attention next

With CmdBrief

One persistent workspace for every product

Build, launch, growth, and review work stay attached

Needs-action alerts show where a decision unlocks progress

Saved workspaces restore the complete working setup

Tasks, agent state, git signals, and browser context make it visible

Local-first, verifiably

Your code never becomes our product.

CmdBrief is a local Rust app, not a cloud IDE, and it ships no usage analytics. Repositories and workspace state remain on your Mac. It contacts cmdbrief.com to check your subscription and sends redacted crash reports to Sentry (EU); agent CLIs and the optional voice assistant reach their providers only when you use them.

Repositories and workspace state are stored locally; agents receive the context you send Session browsing uses local metadata plus bounded local prompt and response previews. Crash reports go to Sentry (EU): the error and stack trace with your home path removed — never terminal content, prompts, responses, or files. Debug builds never report. Secrets referenced as env vars; keys and tokens in the macOS Keychain Mandatory in-app confirmation applies to MCP-staged workspace and workflow actions. CmdBrief is local-first and ships no usage analytics. It contacts cmdbrief.com to check your subscription, and sends crash reports to Sentry (EU) so crashes can be fixed — a crash report carries the error and stack trace with your home path removed, never your terminal content, prompts, responses, or files. Agent CLIs and the optional voice assistant reach their providers only when you use them. When Cursor usage meters are shown, CmdBrief calls Cursor’s dashboard usage endpoint with your local Cursor credential.

Keep every product moving from one place.

CmdBrief is for technical founders running Claude Code, Codex, or other agent CLIs across real products. Connect your first workspace and keep building, launching, growing, and reviewing a whole product portfolio from one place.

Generally availablemacOS 26+Claude Code, Codex, Grok CLI, Kimi CLI, OpenCode, and Cursor CLIMonthly or annual billing14-day money-back guarantee

10 questions

  • CmdBrief is the native Mac workspace for technical founders running multiple products. It gives every product a persistent home for Claude Code, Codex, Grok CLI, Kimi CLI, OpenCode, and Cursor CLI, plus tasks, terminals, files, browser context, live agent status, usage meters, and session resume.

  • CmdBrief is built first for technical founders who personally build, launch, market, and review several products. It is most useful when switching between products means switching repositories, agent sessions, tasks, browser tools, and operating context.

  • Claude Code, Codex, Grok CLI, Kimi CLI, OpenCode, and Cursor CLI get the full supervision layer: live working, needs-action, completed, and failed states, notifications, and session resume. Usage meters cover Claude Code, Codex, Grok CLI, OpenCode Go plans, and Cursor CLI. Any other CLI can run in a regular terminal pane, but it does not report agent status.

  • Ask about agent status, workspaces, usage limits, approved terminal output, and project files after granting session-scoped workspace reading. Voice Agent can start or resume any supported agent and send dictated instructions; those instructions are translated into technical English before they reach an agent. Every state-changing action waits for local confirmation in CmdBrief.

  • OpenAI Realtime and xAI Grok are available. You can use a language supported by the selected provider and configure the assistant’s reply language. Language availability and accuracy vary by provider; each provider requires your API key and bills usage separately.

  • CmdBrief keeps product tasks, terminal sessions, source files, diffs, and browser panes in the same persistent workspace. You can coordinate launch checks, marketing deliverables, or traffic-driven implementation without pretending CmdBrief replaces your deployment, publishing, analytics, or search tools.

  • Not as a shipped native integration. Keep the analytics, search, CMS, or campaign tool you already use open in a browser pane, capture the next outcome as a task, and launch Claude Code, Codex, or another supported agent for bounded implementation work. Publication and measurement remain in the authoritative tool.

  • CmdBrief is local-first: repos, terminal history, and workspace settings remain on your Mac. Agents connect to their providers under your accounts, and account, billing, and optional voice features can use network services. Session browsing uses local metadata plus bounded local prompt and response previews.

  • Yes. CmdBrief is a native Apple-silicon Mac app requiring macOS 26+. Native pieces such as the menu-bar system monitor and notifications are part of why it is Mac-first.

  • Create your account with your email. We verify the email, then you can connect your workspace and start using CmdBrief on your products.