Cofounder Docs
Multiple Companies
Run more than one company under one account — active selection, per-command scoping, and token binding.
One Cofounder account can run many companies, and everything — knowledge, connections, resources, events, billing — stays scoped to one of them. So the only real question is which company a command is aimed at.
The active company
The CLI remembers your selection:
| MCP | CLI | API |
|---|---|---|
company_list_memberships | cofounder company list | GET /cofounder-cli/v1/company/memberships |
company_get | cofounder company show | GET /cofounder-cli/v1/company |
| — | cofounder company switch | — |
| — | cofounder company use <org-id-or-slug> | — |
company switch asks you to pick; company use <org-id-or-slug> sets the
default without prompting.
Aim a single call
Override the saved default when you need to:
--company-id <uuid>— a global flag on any CLI command.COFOUNDER_COMPANY_ID— pins the company for the whole shell or agent environment.
On MCP, every tool takes an optional company_id argument — leave it out
and the call goes to the company your token names.
Token scope
A bearer token carries a company claim (cf), and tokens minted from the
CLI inherit whichever company was selected at the time.
The overrides above work for session tokens. API keys don't bend: a key is
bound to the company it was minted under, and the API rejects a company_id
naming any other company — an Acme key can never act on Initech. If you run
two companies, mint a key for each — see
API Keys and Scripting.
Delete a company
cofounder org delete <org-id> --confirm "DELETE COMPANY"
cofounder org start-fresh <org-id> --name "NewCo" --reason <category> --confirm "START FRESH"Both are destructive, both demand the exact confirmation phrase, and neither
has an undo — preview with --dry-run first.
Next steps
For credentials that don't depend on an interactive login, see API Keys and Scripting.