The setup checklist
The setup checklist is the list of what is left before your first agent can start. It is titled Finish setting up, and it appears on your home dashboard, on a workspace, on a project and on an environment — the surfaces where you would otherwise try to launch something and be turned away.
Because signup already created your workspace, three environments and a Scratchpad project, the list is short.
What it gates
Launching an agent, and nothing else. Everything else in the app works with the checklist incomplete: you can browse, create a workspace, create a project, invite people, change settings. The only thing an incomplete checklist stops is starting a runtime.
You can tell which step you are on, because the launch button says why it is disabled rather than just refusing:
| The launcher says | Which means |
|---|---|
| Connect a coding agent first | No coding-agent credential yet — step 1 |
| Deploy a controller for the environment | Nothing has connected to your environment yet — step 2 |
| Connect an environment first | The workspace you are launching in has no environment. Your first workspace has three; one you created yourself starts empty — create one |
The two steps
- Add your coding-agent credential. → Step 1
- Set up your environment — in practice, connect a controller to the one you already have. → Step 2
That is the whole list. Two things are deliberately not on it:
- GitHub is not a step. You need it only to import a repository, so it has its own page. → Connect GitHub
- Creating a project is not a step. You already have Scratchpad, which is there precisely so your first launch has somewhere to go.
Which environment step 2 is about
Your organization has three environments. The checklist is about sandbox — the one marked as
the workspace default, and the one interactive work runs in.
That is not a coincidence: the checklist resolves the same environment a launch would, which prefers the workspace default, then any sandbox-role environment. So the controller you connect in step 2 is the controller your first agent will actually run on.
build and deployment need their own controllers when you come to use them, attached the same way
from the Environments page. Neither is required to start working.
Skipping and resuming
The checklist is advisory, not modal. Skip for now dismisses it and collapses it to a compact Resume setup banner in the same place. The dismissal is remembered per surface, in your browser, so skipping it on one project does not hide it everywhere — and it never means "done". Resume setup brings the full checklist back.
Because the dismissal lives in your browser's local storage, it does not follow you to another browser or another device, and clearing site data brings the checklist back. That is intended: the work is not finished, only hidden.
When it is done
When every step is satisfied the checklist becomes a You're all set card recapping what you configured — the coding agent, the environment and its type, the controller. Worth reading once: those are the values you will be asked about if anything goes wrong later.
The checklist evaluates continuously rather than on a submit button, so step 2 completes by itself the moment your controller connects. You do not have to come back and tell it.