SWIRLS_
Platform

Local Development

Author, validate, and deploy .swirls files from your machine.

The Swirls CLI is for authoring .swirls files from your machine: validate the files, generate types, configure a Cloud project, and deploy for inspection in the Portal. Local workflow execution and local agent chat are not supported.

Install the CLI

curl -fsSL https://swirls.ai/install | bash
npm install -g @swirls/cli

Verify the install:

swirls --version

Local development workflow

Install CLI → Login → Create project → Configure → Write workflows → Validate → Generate types → Deploy → Inspect

Authenticate

Log in before creating or deploying a Cloud project:

swirls auth login

Create or select a project

Create a new Cloud project:

swirls project create

List existing projects:

swirls project list

Configure the project

Generate swirls.config.ts in your working directory:

swirls configure

The command prompts for your project ID and writes the config file:

import { defineConfig } from '@swirls/sdk/config'

export default defineConfig({
  projectId: '<your-project-id>',
  genPath: 'src/swirls.gen.ts',
})

The CLI reads swirls.config.ts to determine which project all commands apply to. swirls config is an alias for swirls configure.

Write .swirls files

Write your workflow definitions in .swirls files. See the Swirls Language reference for syntax and available node types. Use swirls doctor to validate your files:

swirls doctor

Generate TypeScript types

Generate TypeScript types from your project's form definitions:

swirls form generate

The CLI writes generated code to the path configured in genPath. Import these types in your application for end-to-end type safety around form payloads and project integrations.

Deploy for inspection

Deploy the project to Swirls Cloud:

swirls deploy

After deploy, open the Portal to visually inspect the compiled project and verify the workflows, triggers, forms, and schemas Swirls parsed from your files. Free deploys do not include workflow execution or agent chat.

What local development does not do

Local development does not execute workflows, start a worker, or open an agent chat session. Use the local tooling to author and validate .swirls files, then deploy to Cloud for inspection.

Next steps

On this page