Cofounder Docs
Cofounder Docs

Cofounder CLI

Run a Company End to End

Recipe: from a fresh Cofounder account to a provisioned company with an agent actively working it.

The goal here: a company with knowledge, provisioned resources, and an agent working its roadmap, starting from nothing.

Steps

Sign in

cofounder auth signup --email you@acme.com for a new account (password via --password or COFOUNDER_PASSWORD), cofounder auth login for an existing one. Or connect an agent through MCP and skip the CLI entirely.

Create the company

company_create / cofounder company create "Acme Analytics". See Create a Company. The new company becomes your active selection.

Import what you know

company_knowledge_import previews, then writes on confirm. The command, provider list, and report contract are in Company Knowledge. Then drop files into the Library with cofounder library upload.

Run managed setup

company_setup_start / cofounder company setup, then poll company_setup_get or watch live with cofounder watch company. See Managed Setup. Inspect the result with cofounder company resources list; each resource shows live or a gap with its reason.

Hand work to the agent

roadmap_get → roadmap_nodes_prompt_get on the first node. The prompt hands your agent a brief, and it works the node itself. Follow progress through events_list or cofounder events tail. See Watch It Run.

Troubleshooting

  • Setup stalls on a provider: once it's fixed, grab the failed run's run_id from cofounder company setup status and pass it to cofounder company setup retry <run-id> (the company_setup_retry MCP tool takes the same id).
  • A resource shows a gap: resources_get explains why. Billing failures respond to cofounder company billing resources retry.
  • The agent can't see a file: it was probably uploaded to a different company's Library. Check the active company with cofounder company show.

Next steps

Have existing code to bring in? Import a Repo and Ship a Change binds a repository to the company and deploys it.