Cofounder CLI
Import a Repo and Ship a Change
Recipe: bring an existing repository under the company, work it locally, and deploy.
The goal here: an existing codebase bound to the company, with agents able to work it locally and ship through its hosting provider.
Steps
Import the repository
code_repository_import_start / repo import owner/repo /
POST /cofounder-cli/v1/company/repository/import. When Vercel access clears, run
repo import continue to finish the link, and track progress with
repo import status; large repos take a moment.
If GitHub access is missing, the error includes a CLI dashboard link. Open it,
authorize your GitHub account, and install or configure the Cofounder GitHub
App for this repo. Recheck access, finish connecting if prompted, then retry
the original import command. The dashboard grants access; it does not run import.
Clone and orient
cofounder repo clone pulls the bound repo locally, and
cofounder repo status inside it reports the production branch, the
last production deploy, every open PR, and which branches belong to
agents.
Make the change
Branch, commit, push. cofounder repo push-token mints a push token
when the local clone needs one, and repo handoff marks the branch when
a different agent takes over.
Deploy
hosting_deploy /
cofounder hosting deploy /
POST /cofounder-cli/v1/company/repository/deploy. Watch hosting_deployments_get for
the rollout and hosting_deployments_readiness_get before you
call it done.
Troubleshooting
- GitHub approval is pending: ask the GitHub organization administrator to approve access, then recheck in the dashboard. If the access link expires, retry the import for a fresh link; the dashboard can rediscover approved access.
- Different GitHub installation: finish connecting in the dashboard to grant access for this repository. The import remembers its installation and preserves the company's existing GitHub connection for other repositories.
- Import never completes:
repo import statusnames the blocker; the generatedcode repository-import cancelcommand backs it out cleanly. - Deploy is green but the app 500s:
hosting_deployments_eventscarries the provider's build and runtime log lines. - Supabase schema drift:
cofounder database migrations listshows what applied;database migrations applyruns what's pending.
Next steps
Watch It Run covers the event stream behind every deploy, and Run a Company End to End shows the full account-to-agent path.