Run commands and coding agents on existing cmux Cloud machines, monitor work that continues after disconnection, and present results through workspaces or service URLs. The skill guides machine selection, background execution, and result verification.
Operate cmux Cloud machines, run durable remote commands or agents, and present their workspaces or services. Use for cmux vm/cloud tasks; backend implementation belongs to cmux-backend.
Review the instructions the agent will receive before you install.
Use an existing machine and a workspace for the task. Machine terminals persist when panes close or the Mac disconnects. Work headlessly; open a pane or share a URL when there is a result for the user to inspect.
cmux vm --help
cmux auth status
cmux vm ls --json
cmux vm route --json
On the Mac, host operations need the app, sign-in and its private tunnel. Inside a
machine, use cmux self --json and the guest's help; read guest operations
for its supported subset and auth. Installed help is authoritative when versions differ.
route inspects placement without creating a machine. Read would_provision and
the backend's limits/capabilities; do not assume a plan cap, memory size or
provider feature. Reuse the router's pool machine, or explicitly pin an existing
target with --machine <id>. Base is the user's persistent work. Prefer another
workspace on a machine to another machine.
After identifying an authorized target, choose the operation:
| Need | Start here |
|---|---|
| Bounded command and exit code | cmux vm run --machine <id> -- <command> |
| Detached coding agent | cmux vm agent --machine <id> --agent codex --no-open -- "<task>" |
| Project with a dev layout | cmux vm dev <id> --dry-run --json, then the approved plan |
| Observe without opening panes | cmux vm tree <id> --json, cmux vm terminal read <id> <term> |
| Completion and full output | cmux vm terminal wait-exit <id> <term>, then terminal output |
Read the selected verb's --help before adding flags. Retain the machine,
workspace/terminal identity and actual exit result. A finished wait is not proof
that tests passed. Use vm open/workspace open to present verified results;
closing a view does not stop the machine terminal.
--no-open, --detach or --print while working. Focus changes are intentional.
workspace rm kills its terminals; workspace close detaches them.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Organize cmux windows, workspaces, and split panes so an agent can target the right terminal reliably. Create terminals with startup commands, move or reorder panels, change focus, and flash a panel to identify it.
Guide substantial Swift changes in cmux with rules for package boundaries, dependency direction, state management, concurrency, and API documentation. Structure code so public package types can be tested without launching the app.
Guide cmux backend changes with consistent rules for Effect, a TypeScript library for structured error handling. Covers Cloud VM state, database migrations, provider integrations, and authentication and payment checks so changes follow the intended architecture.
Maintain cmux billing code with guidance on Stripe checkout, pricing, subscriptions, and access rights. It maps the relevant services and provides workflows for testing purchases, handling payment events, and rolling out billing changes.
Automate browsing in cmux panels without taking focus away from current work. Target a specific panel to open pages, fill forms, click controls, wait for page changes, extract content, and inspect download history.
Capture cmux windows as screenshots or video clips from the CLI. Create visual evidence for pull requests and bug reports, with region selection and captions to explain drags, animations, or layout changes.