Contact CmdBrief

Tell us how you operate your product portfolio.

Use this page for getting started, product questions, and support—especially if you build, launch, market, and review several products yourself. We reply within one business day.

Fastest way to reach us

Send a message instead of an email.

The form routes your request by topic so it lands with the right person, keeps your details out of a mail client, and comes with a response promise: one business day.

Contact form

Send us a message.

We reply within one business day. This form is not tracked — your message and email are used only to reply.

Contact paths

Choose the route that matches the request.

Getting-started, product questions, and support details each have a direct route, so the conversation starts where it can be answered fastest.

Contact

Getting started

Create your CmdBrief account to run the workspace across your products, or tell us where building, launching, or reviewing results loses context.

Create your account
Contact

Product questions

Ask about CmdBrief features, supported workflows, local-first boundaries, signed macOS builds, or future product direction.

Send a message
Contact

Support

For install, entitlement, or workflow feedback, include your macOS version, agent tools, and a short description of what happened.

Email support
Community

Find answers without opening a support thread.

Most questions are already answered in the guides or on X. Try these before or after you write in.

Documentation

Documentation and guides

Setup, workflow, and agent runtime guides that answer most product questions without waiting on a reply.

Browse guides
X

X (Twitter)

Product announcements, release notes, and quick questions from the founder account.

Follow @cmdbrief
Email

Email

For longer product questions, support requests, and workflow details. Replies within one business day.

Email [email protected]
Support details

What to include in a support email.

Short, concrete reports are easiest to act on. Include what you expected, what happened, and the local workflow context around the problem.

SystemmacOS version and hardware type
AgentsCodex, Claude Code, or other tools involved
WorkflowProduct count, current job, panes, or session state
Quick notes

Simple boundaries.

Use email or the form for product questions or support.
Do not send secrets, private keys, or proprietary source code.
Include your macOS version and the agents involved for workflow issues.
Ready to run the loop?

Create your account and start operating your products from one workspace.

Questions can go by message, but the fastest path is creating your account and trying CmdBrief on your real multi-product workflows.