Cofounder CLI
Cofounder connects you and your coding agent to the company behind your product: persistent resources and operations such as hosting, databases, domains, email, payments, and analytics.
Keep using your local tools for code, Git, and tests. Use Cofounder to manage company resources, permissions, approvals, and status in one shared place. Your next session can pick up from the company's current state instead of reconstructing it from chat history.
Get started
You'll need Node.js 22 or newer.
npm install -g @generalintelligence/cofounder [email protected]
cofounder auth login
cofounder company list
cofounder --help
Select a company with cofounder company use COMPANY_ID, replacing COMPANY_ID with an ID from the list. Starting a new company? Run cofounder company create --help. Add --json to commands when you need structured output for scripts or agents.
Vercel CLI
The install command above installs the official vercel package alongside Cofounder. Both Cofounder environments use that same vercel command. Request credentials with cofounder hosting credentials create --resource-id <id> --json, then export its env fields and run Vercel commands directly. Cofounder does not automatically renew these credentials.
If you already have a compatible global Vercel installation, you can omit [email protected] from the install command. Global Vercel updates are managed separately from Cofounder. Project-local Cofounder installs include the pinned Vercel dependency and its ordinary vercel executable automatically.
Find your next milestone
After selecting a company, see where it stands and what to work on next:
cofounder roadmap get
The roadmap shows your recommended milestone and progress by department. Inspect a milestone with roadmap nodes get --node-key <milestone-key>. Viewing the roadmap doesn't start work.
Working with your coding agent
Use local tools to build and test your project. For company operations:
- Find the Cofounder Capability that matches your goal—the instructions and tools for that kind of work.
- Check the company's existing resources and requirements.
- Follow the Capability's instructions, use its tools, and respect required approvals.
- Verify the outcome and keep its receipt or evidence.
Cofounder is the source of truth for its managed resources, permissions, approvals, and status. Reuse those resources rather than creating parallel infrastructure directly with a provider when Cofounder supports the work.
If multiple resources match, ask which one to use. If Cofounder doesn't support the work, say so before taking another path.
A project-local .cofounder/ directory may identify the project. It must not contain credentials or be treated as live company state.
Production and staging
This package runs cofounder and connects to https://api.cofounder.co by default. Saved login and settings live in ~/.cofounder, outside your project. Production and staging commands can be installed together and keep separate saved logins. Explicit COFOUNDER_CONFIG_DIR and API URL overrides remain supported.
Updates and supported platforms
Update with npm install -g @generalintelligence/cofounder@latest.
Supported: macOS ARM64 (Apple Silicon; Intel Macs are not supported), Linux glibc x64/ARM64, and Alpine Linux musl x64. You don't need Bun. Keep npm optional dependencies enabled; reinstall if the platform package is missing.
Documentation
Visit the Cofounder docs for guides to the workspace, roadmap, company resources, and more. Use cofounder --help for available CLI commands.