Migrating from the Web App

Used Cofounder 2 or Cofounder Canvas? Your account and companies carry over, and your own agent now runs them through MCP or the CLI.

If you used Cofounder 2 or Cofounder Canvas, you keep the same account and companies. Your companies, files, connections, and billing carry over unchanged. What changes is who does the work: your own agent, through MCP or the cofounder CLI. To check on things yourself, use the dashboard at app.cofounder.co/os.

Where Things Went

Web app	CLI / MCP
Workspace and departments	The company: same scope, one selection
Library tab	, tools: same files
Managed services (GitHub, Vercel, Supabase)	, , , , command families
Agent tasks	Roadmap nodes: ,
Past agent conversations	Read-only commands and tools
Settings	,

Read Past Conversations

Your agent can read your old Cofounder conversations to see what was decided and plan what to do next.

cofounder chat sessions list
cofounder chat sessions list --scope org
cofounder chat sessions get --session-id <session-id>
cofounder chat sessions messages list --session-id <session-id>

The MCP tools are chat_sessions_list, chat_sessions_get, and chat_sessions_messages_list.

Lists show your own conversations in the selected company. --scope org adds other people's conversations in that company.
Results come in pages. Pass the returned cursor with --cursor to read older ones.
Message pages hold whole turns, about 50 messages each. The older --limit flag doesn't change that.
--include-prior-context shows messages from before a conversation's most recent context reset.

These tools only read. Old Cofounder agents can't be restarted, so your own agent does all new work.

First Steps

There's nothing to move, since your data stayed where it was.

Connect your agent or install the CLI and sign in with the account you already have.
Run cofounder company list. Your companies are already there.
Run cofounder company resources list. So is everything you set up.

The Quickstart shows your agent running a company from there.