CLI

You do not need the CLI to build and publish with Continual. The usual workflow is to work with the agent in a thread, review the preview, and ask it to publish. The agent can use the CLI as part of that work.

Run the CLI in a terminal on your computer, from an app repository you already have checked out. Source in Continual is the repository browser. The CLI's link command connects your local checkout to a project; it does not download the project's source.

If your project is connected to GitHub, clone that repository using your GitHub access, then follow the steps below. For work inside Continual, keep using a thread: managed executions already supply authentication and project context.

Install and authenticate

The Continual CLI requires Node.js 24 or later. Install it in the package where you develop the app, then authenticate with a user API key.

Use workspace settings > API keys to manage keys. Login saves the key outside the repository. Use continual logout to remove the saved login.

Project and branch context

Link selects an existing project and saves its identity in .continual/project.json, adding that file to .gitignore. You can select a project directly with --project <project-id-or-url>.

The CLI resolves the current Git branch in the linked project. Managed Continual executions supply project, branch, and a temporary execution credential automatically; skip login there. Use --branch on branch-aware commands to override the target.

Prepare local development

env pull writes the branch environment to .env.local. app env reserves the app URL and writes its URL variables before a build that needs them. Keep environment files containing secrets out of version control.

typegen generates typed helpers for project and connection tools. It writes the requested entry file and a sibling directory of generated modules; commit or ignore both together. Filter tools with repeatable --connection or --tool flags.

Build and deploy

Create an app with your framework's tooling. In its package.json, declare continual.key, continual.name, and continual.output for the built artifact directory.

The repository owns the build. The deploy command packages and publishes its output; dry-run validates without uploading or publishing. The CLI also supports development URL deployments.

Check the selected project and branch before deploying. Run pnpm exec continual --help or a command's --help for available options.