Cofounder Docs
Install the CLI
Install the cofounder binary with npm, sign in, and keep it up to date. Node.js 22 or 24 required.
The cofounder CLI puts the same operations in your terminal. Install it if
you want to drive Cofounder by hand, wire it into scripts and CI, or reach
the surfaces MCP doesn't cover.
Install it
You'll need Node.js 22 or 24. The npm package is private, so run
npm login first — your account needs access to the
@generalintelligence organization.
npm install --global @generalintelligence/cofounder@latest vercel@59.19.0The pinned vercel package is the version the deploy commands are tested
against. Leave it off to keep a compatible global install you already have;
project-local installs (npm install @generalintelligence/cofounder) carry
the pinned dependency themselves.
Check it worked:
cofounder versionSign in
cofounder auth loginThat opens a browser sign-in and stores the credential under ~/.cofounder.
No account yet? cofounder auth signup --email you@acme.com creates one —
the password comes from --password or COFOUNDER_PASSWORD.
| Command | What it does |
|---|---|
cofounder auth whoami | Show the signed-in account |
cofounder auth token | Print a bearer token for scripts and MCP configs |
cofounder auth logout | Remove the saved credential |
Keeping it current
cofounder upgradeThat prints the npm command matching how you installed — the CLI never downloads or executes anything itself, so run what it prints.
When to skip it
An agent on the hosted MCP server
doesn't need the CLI at all. Install it when you want the human terminal
path, API keys, or the surfaces MCP doesn't cover (Stripe objects, auth
commands, the mcp config helpers).
Next: the Quickstart creates a company and gives your agent its first task.