Deploying your app

Ship to production from the IDE button or the CLI, add custom domains, read logs, and verify with the project’s own checks.

Ship it

The IDE’s Deploy button and the CLI run the same pipeline: build, checks, ship, health verification. From the terminal:

mlcl login                            # once
mlcl deploy --project <id> --follow   # watch it through
mlcl deploy status --project <id> --deployment <id>   # (also: list / cancel)
Tip

CI, not a human, should run deploys: mlcl deploy workflow-github --project <id> (or workflow-gitlab) writes a ready-made workflow — --apply to commit it. To run mlcl itself in CI, set MOLECULE_TOKEN to a personal API token.

Custom domains

mlcl domain add app.example.com --project <id>
mlcl domain list --project <id>               # shows each domain id
mlcl domain verify <domainId> --project <id>

add prints the DNS records to set; verify confirms them and issues the certificate.

Logs and checks

mlcl logs --project <id> --stream
mlcl check                            # in your app folder: typecheck, lint, build, unit, e2e

check discovers the project’s own scripts and runs them concurrently, printing one compact report with the first actionable error of each failed step. The same verification is available to agents as the check_project MCP tool.

Snapshots, staging, egress

  • Snapshots: mlcl snapshot create/list/restore/rm --project <id> makes point-in-time copies of the sandbox you can roll back to.
  • Per-branch staging: mlcl stage up (with down / status / logs).
  • Outbound egress: sandbox network calls are allowlisted by default; approve a host with mlcl egress approve <host> --project <id>.