The guided walkthrough

A four-step terminal tour of providers, crew, flows and your first run that you can skip or quit and pick up later.

In simple words

The dashboard’s More > Setup page is the primary guided path: numbered steps, live check results, a Fix what’s safe button. vibe welcome is the terminal-native version.

vibe welcome

It walks four steps: a provider, a crew, your flows, then your first run. Quit halfway and it picks up where you stopped. Skip any step. --reset starts over.

Tip

It asks questions, so it needs a real terminal. In a script or in CI it prints the commands to run by hand and exits without touching anything.

What each step settles

Providers Which coding-agent CLIs you already have, and which are logged in.

Crew The six workers, and which model each one runs on.

Flows Which recipes this project can run, and which is the default.

First run A real task, start to finish, so the vocabulary lands.

Did you know

The tour is resumable because it writes as it goes rather than at the end. Quit after step two and you have a working provider and crew, not a half-written config.

The four steps

Providers - the coding CLI that runs the model, such as Claude Code or Ollama. This step runs vibe provider setup.
Crew - your team of AI workers. Install a ready-made one (Fast, Thorough, Cheap, or Local), or build your own later on the Crew page.
Flows - the ordered list of steps a run works through. You see the flows you have, and how to install more from the flows hub.
Your first run - a small task to try next.

Each step opens with a short explanation, then asks whether to continue, skip or quit.

It remembers where you left off

A step counts as done only when it succeeds, so a failed step is the one you land on next time. Progress lives in .vibestrate/welcome-state.json, which records which steps you’ve been through and nothing else. Delete it, or run --reset, and your providers, crew and flows stay as they are: those settings live in project.yml.

vibe welcome --reset

If the project isn’t set up yet

The tour offers to run vibe init for you. Say no and it stops there, leaving you two commands:

vibe init
vibe welcome

The dashboard does the same with the Setup page’s Initialise this project button.

Three ways to work

Dashboardvibe ui - runs, crew, flows, source and setup on 127.0.0.1:4317. The primary surface.

Interactive shellvibe - the same surfaces, terminal-native.

Commandsvibe run "your task" - the automation path, for scripts and CI.

Keep the change → - what to do with the branch your first run leaves behind.