Founder portfolio workspace

Keep every product and every agent moving.

CmdBrief keeps Claude Code, Codex, tasks, terminals, files, diffs, and browser context attached to each product—so you can see what is working, blocked, finished, or waiting without rebuilding context.

Apple silicon · macOS 26+ Local-first workspace Private beta
Why nowAI lets one founder move several products at once. Keeping the portfolio coherent is the new bottleneck.
  • AI increased founder capacity across products, launches, and daily operations.

  • Every product creates more state across code, tasks, browser tools, and metrics.

  • Founder attention is the constraint and the right next decision keeps the portfolio moving.

Recorded from the beta build, not a mockup — Claude landing an integration test and running cargo while Codex writes the changelog 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 Claude Code and Codex; and dictate the next instruction without navigating between panes.

  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 Claude Code or Codex.

  3. Stay in control

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

CmdBrief beta with the Voice Agent panel active beside Claude Code and Codex panes while a local action awaits confirmation.
Recorded from the CmdBrief beta, not a mockup — Voice Agent beside live agent panes with a local confirmation pending.

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

Portfolio control

Keep every product moving without keeping every detail in your head.

Know what needs you, across every product

Claude Code and Codex sessions report working, needs action, completed, or failed. Attention rolls up across panes, tabs, and product workspaces so blocked work cannot disappear.

Catch decisions before work stalls

When an agent stops for a question, plan approval, or permission prompt, native notifications tell you which product needs a decision instead of leaving it buried in a terminal.

Turn the next job into an agent run

Assign a product task to Claude or Codex. CmdBrief carries the task and project context into a new pane, tracks the run, and keeps the work attached to the product.

Protect your agent runway

When a provider exposes reliable usage-window data, CmdBrief keeps it visible so you can decide where limited agent capacity creates the most progress.

Resume the right product thread

Browse local sessions by title, directory, git branch, tokens, and runtime, then reopen the exact Claude Code or Codex thread without reconstructing context.

A real terminal for serious work

A full xterm-class emulator with GPU-rendered text, split panes, durable scrollback, and command blocks annotated with exit status, duration, and git state.

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 apps, campaign tools, and analytics dashboards can stay open in workspace panes
  • Local dev-server URLs are detected in output, deduplicated, and ready to open in one click
  • Repo-native and SKILL.md actions turn repeatable product work into reusable commands
  • Native notifications, menu-bar status, and system stats keep the portfolio visible from macOS
Two agents on one repo — Codex drafting the changelog while Claude reads the code.
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.

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.

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.

Split-pane layouts

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

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.

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.

Menu-bar monitor

A native macOS menu-bar app with live CPU, GPU, RAM, and battery — and agent attention at a glance.

Built for speed

Rust end to end, with a WGPU renderer that draws terminal text pixel-identical to the UI. Fast under load, easy on the battery.

Safe imports

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

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. Repositories and workspace state remain on your Mac; agent providers, account and billing services, and optional voice services receive traffic only when those features are used.

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 stay local Secrets referenced as env vars, never stored Mandatory in-app confirmation applies to MCP-staged workspace and workflow actions. CmdBrief is local-first. Agent providers, account and billing services, and optional voice providers may receive traffic when you use those features.

Keep every product moving from one place.

The beta is for technical founders using Claude Code or Codex across real products. Request access and help shape the workspace for building, launching, growing, and reviewing a product portfolio.

Private beta access

Join the beta waitlist.

Private betamacOS 26+Claude Code and CodexWaitlist access
FAQ

Questions, answered

CmdBrief is the native Mac workspace for technical founders running multiple products. It gives every product a persistent home for Claude Code, Codex, 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.

Deep supervision — live working, needs-action, completed, and failed states, notifications, usage meters, and session resume — is built for Claude Code and Codex. Other CLI agents can run in regular terminal panes, but they do not get the agent-specific status layer yet.

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 Claude Code and Codex 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 or Codex 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. The private beta 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.

Request private beta access with your email and explicit contact consent. You will be added to the waitlist and may be contacted if your workflow matches an upcoming invite wave.