Contact CmdBrief

Tell us how you operate your product portfolio.

CmdBrief is in private beta preparation. Use this page for beta access, product questions, and support for invited testers—especially if you build, launch, market, and review several products yourself.

Contact paths

Choose the route that matches the request.

Keeping beta access, product questions, and support details separate helps route the conversation without adding a heavy contact form.

Contact

Private beta access

Tell us how many products you run, which agent tools you use, and where building, launching, or reviewing results loses context.

Join the beta waitlist
Contact

Product questions

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

Email CmdBrief
Contact

Beta support

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

Email beta support
Support details

What to include in a beta 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 the beta waitlist for early access requests.
Use email for product questions or beta support.
Do not send secrets, private keys, or proprietary source code in a support email.
Ready for the beta?

The waitlist is the best path for access.

Product questions can go by email, but beta access starts with the waitlist so invites can prioritize technical founders operating real multi-product workflows.