SymvibeDocs
  1. Docs
  2. Getting started
  3. Quickstart

Your first board

This walk-through takes about five minutes. It assumes Symvibe is installed, you are signed in, and at least one agent CLI already works in Terminal.

Updated October 22, 20262 min read

On this page

Open a repo's board#

  1. Pick a repo on the home screen

    Click its row, or choose it in the repo pill of the compose bar and press Dispatch. No repos yet? Use Add a repo or ⌘O and choose a folder.

  2. Look around

    The board opens on Workspace 1. Tools are on the left rail, things to insert on the right rail, the command bar runs along the bottom and the top right shows who is live and who needs you. Board basics covers all of it.

Start three agents#

Use whichever way is closest:

  • Press T for Spawn agent and click an empty spot. The console runs the armed agent: your default agent, or the last one you picked in the console flyout, in All agents or on the empty board. If no agent is armed yet, the flyout opens so you can pick one.
  • Click New console in the command bar and pick Claude, Codex, Gemini, Grok, OpenCode or an empty shell.
  • Right-click empty canvas and choose Spawn agent.
  • Type it in the command bar: spawn 3 claude.

Each console is a real terminal running the CLI in your repo folder, with a short name such as Otto, Maya or Kai so you can address it. If the CLI is not on your PATH, the console opens your shell instead and tells you.

The Spawn 4 composer: choose an agent for each slot and launch them together.

Give them work#

Click inside a console and type, exactly as in Terminal. To talk to several at once, use the command bar (⌘K):

  • @Otto run the test suite and report failures goes to Otto only.
  • Hold Space on the board, say what you want and let go to send it.

The orchestrator types your order into the consoles and submits it, as if you had typed it and pressed Return. When one task is meant for several agents, it splits the work instead of pasting the same prompt everywhere. How orders reach your agents explains the rules.

Agents in one folder share its files

Three agents in the same checkout can edit the same file at the same time. Give each writing agent its own git worktree; read-only work such as reviews can share. The worktrees guide shows how.

Watch their status#

Every console header carries a status pill. STARTING and WORKING come from the terminal itself. For NEEDS YOU when an agent waits on a permission or a question, and READY when it finishes a turn, turn on live agent status for Claude Code and Codex.

Press N to jump to the console that needs you, and X to open the Mission Map with every console in one view.

Close and come back#

Quitting Symvibe ends every console's process, and asks first when agents are running. The board is saved. When you reopen the repo, each console starts fresh in its place, and for Claude Code, Codex, Gemini and OpenCode a card offers to resume the last conversation. Resume and quitting has the details.

Keep going#

Core conceptsThe words the rest of the docs use. The command barTyped and spoken orders, mentions and the thread. Groups and teamsName a group, give it a role, spawn up to 12 at once.

Something on this page does not match what you see in the app? Write to hello@symvibe.com or tell us in the Discord, and we will fix it.