Skip to content
Browse documentation
start here

Choose a Starter

Compare the web, interactive Agent, and durable Worker Starters before creating a new application from one.

Available Starters

A Starter is a Recipe that the CLI copies once into a new directory as your own editable source. The CLI does not regenerate it later. Create one application from the Starter closest to your product; the release you downloaded lists which Starters it includes.

smoothie-starterA browser interface, client-side routing, a shared Service contract, and an HTTP server. Start here for a web application; it needs no model, database, or credentials.
interactive-agentAn Octane chat interface with server-side Agent execution, SQLite history, and approval-gated note writes. Sending messages requires an OpenAI Responses model (SMOOTHIE_MODEL) and an OPENAI_API_KEY kept on the server; each message is a billable request.
durable-workerSeparate TypeScript API and Worker processes backed by Redis and Postgres. Requires Docker Compose, free local ports 55432, 56379, and 43120, environment configuration, and migrations. Its service tests are skipped, not passed, until Postgres and Redis are running. It is not a serverless Starter.

Inspect a Starter

bash
smoothie recipe list
smoothie recipe show smoothie-starter

Explore the Recipe pages for each Starter's file map and adaptation boundaries.

Run these commands inside your project after acquiring a release. They verify and use the selected source and bundle. For a separately stored release, add --from /path/to/release/source to each command.

To inspect another Starter, replace smoothie-starter with an id from the list. Show reports the Recipe's kind, declared support status and reason, and file list. Read the Recipe's README in the source release for prerequisites; the dry-run plan from recipe create shows the exact package closure. When using --from, these commands read source only, so verify the paired release first.

After creation

Creation copies only the chosen Starter and the package archives it needs. From then on, your project owns its product behavior, interfaces, contracts, tests, and target configuration; Framework package updates never overwrite them. Keep the adoption baseline and original notices. To change Framework code itself, copy the acquired source to a separate working directory so the verified download stays intact.

Create your first application walks through Smoothie Starter. The same command creates the other Starters, but their configuration, run, and verification steps are in each Starter's README, which is copied into the new application. Interactive Agent's fixed local owner is not production authentication, and Durable Worker's local token and services are not a production deployment.