Core concepts · Symvibe Docs

Symvibe has a small vocabulary. Knowing these words makes the rest of the docs, and the orchestrator, easier to use.

Places#

Repo: A folder you track on the home screen, usually a git repository. Tracking never moves or changes it. Each repo has its own boards, thread and memory.
Workspace: A tab of a repo's board, named Workspace 1, Workspace 2 and so on until you rename it. Consoles in background workspaces keep running.
Board: The canvas of a workspace: 24,000 points on each side, zoom from 20 to 300 percent. What you place on it is saved to disk a moment after each change.
Home screen: Where your repos are listed and presets are dispatched. Symvibe opens on the last repo you had open.

Node: Anything on the board: a console, a note, a kanban, a web tile, a shape, an image, a card.
Console: A node that runs a real terminal: an agent CLI or a plain shell, started in the repo's folder, with a short name you can address, such as Otto. The app sometimes calls a console a lane.
Agent: A CLI from the catalog of 34, such as Claude Code, Codex, Gemini CLI, Grok or OpenCode, or an executable you add yourself.
Default agent: The agent Symvibe uses when you leave the choice to it, such as the lanes of a preset you leave alone. A spawn order that names no agent uses the role's agent, or opens a shell.
Group: Two or more consoles kept together with a name, a role and a tint. ⌘G groups the selected consoles.
Card: A node that shows something rather than runs it: a document, a code file, a Markdown file, project memory, Git branches.

Command bar: The bar at the bottom of every board. You type or speak orders there, and it commands the whole board.
Thread: The command bar's conversation, kept per repo: your orders, the replies and each agent's report.
Orchestrator card: A card you wire to some consoles. Orders given on it reach only those consoles.
Planner: What turns a sentence into steps. Plain orders such as spawn 4 codex are understood on your Mac. Other sentences go to Symvibe's planner service, which uses credits.
Live agent status: An opt-in setting that lets Claude Code and Codex report, through their own hooks, when they are working, need you or are ready.
Mission Map: A map of the command bar, the orchestrator cards, the groups and every console, filtered by status.
Handoff: Passing a task from one agent to a fresh console, usually of another CLI, with a summary of where it stands.
Loop: An instruction Symvibe sends to consoles on a schedule, when they go idle or when their output shows some text. It runs until you switch it off, or until an optional goal, run count or time limit ends it.
Memory: Facts about a repo, or about all repos, that you push into agents as background context.

Studios: Documents, Diagrams, Code and Markdown: views that turn the repo into PDFs and diagrams, and let you browse its code and notes.
Skills: The Claude Code skill files on your disk, with a checkup and an editor.
Preset: A ready layout of consoles and groups. Dispatch one from the home screen or deploy it on a board.
Profile: An extra sign-in of Claude Code or Codex, kept in its own configuration folder. You can add more than one.
Credits: The monthly allowance shared by the planner and spoken replies. Your agents never use credits; they use their own plans.
Yolo: A setting that starts agents with their skip-permission flag. Off by default.

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.