Managed Setup

Managed setup is the fast path to a working company: one run provisions the baseline — repository, deploy target, database, email, billing — then reports what succeeded and what's still waiting on you.

Start a run

cofounder company setup
cofounder company setup status

If a step fails on something transient, don't restart — grab the failed run's run_id from setup status and pass it to retry, which picks up from the failed step.

Phone is the one baseline resource that's opt-in: on the CLI, pass --phone to provision the company's number in the same command (--country and --area-code pick it). The request fires right after the setup run starts — it's not a step inside the run — so if it fails, retry it directly with company phone provision rather than setup retry. On MCP it's always a separate company_phone_provision call.

To watch the run live:

cofounder watch company

Inspect what you got

Every managed resource — the repo binding, the database, the inbox, the phone number — shows up as a company resource with a state, so listing them tells you what's live and what's missing:

Copy the resource_id exactly as the list prints it — connected resources carry composite ids like connected:github, not just UUIDs.

On the CLI there's a shortcut: cofounder company resources show <primitive> inspects by resource type — resources show code for the repository — and prompts when several match. The primitives are the ones resources list prints.

A resource that failed to provision shows up as a gap rather than silently missing. Its detail view explains why, and billing failures point you at cofounder company billing retry-resource.

Next steps

Once the resources exist, Deploy and Operate covers the day-to-day work on them.