What a kit is
A starter kit is a configured harness plus a web app that uses it. Launching one creates the harness in your workspace with its base, model, instructions and limits set, and installs the kit's package as an ordinary plugin, so you can open the harness's settings and change anything.
Each workspace gets its own harness for a kit. Launching the same kit again returns that harness and brings its package and instructions up to the kit's current version.
The kits
- Slides
- Design presentations by conversation, then edit them by hand.
- Sheets
- A spreadsheet where a column can be an agent.
- Dashboards
- Say what you want to understand and your database answers it. Asks for a Postgres or MySQL connection string at launch.
- Videos
- Describe the film and watch the shots arrive on a canvas. Uses the media tools.
- Platform game
- A System One model plays a browser game several times a second while you watch its browser.
- My Workplace
- Hire AI teammates by answering a few questions, then work with them like a team chat.
Launching one
- Open Starter Kits, the first item under Build in the console.
- Each card recommends base and model pairings and marks which ones your organization can run. Choose one, or launch with the recommendation.
- Dashboards asks for a connection string before it creates anything, so a typo costs a corrected form rather than a half-configured harness. Launching it again with a new connection string reconnects it, for example after a password change.
From the API
A launch answers with the harness it created or reused, as {"kit", "harnessId", "route", "created", "harness"}, where route is the kit app's page in the console. Passing "harness": "<id>" runs the kit on a harness you already have instead.
- 404 kit_not_found
- No kit has that id.
- 400 connection_required
- The kit reads a database and its first launch gave no connection string.
- 400 connection_not_used
- A connection string was given to a kit that reads no database.
- 400 invalid_base
- The base is not one your organization can use.
- 400 model_unavailable
- Nothing your organization has connected can run that model on that base.
- 404 harness_not_found
- The harness named in harness does not exist in this workspace.
- 409 kit_conflict
- The harness named in harness already runs another kit.
GET /v1/kits the kits and their recommended pairings
POST /v1/kits/{id}/launch {"base": "claude-code", "model": "claude-sonnet-5.5"}
Dashboards adds {"database": {"engine": "postgres", "connection_string": "..."}}Ready to run this against a live workspace? Keys take under a minute.

