- Docs
- Orchestration
- The command bar
The command bar
The bar at the bottom of every board is how you direct the whole board. Type or speak an order, aim it with an @ mention, and read the replies and the agents' reports in its thread.
Talk to the bar#
- When no console or text field has the keyboard, ⌘K puts the cursor in the bar (inside a console it clears that console instead), Return sends, Esc gives the keyboard back to the board, and Up and Down recall your last 50 commands.
- Hold Space on the board to speak, and let go to send. The mic button works too: hold it, or tap once to start and again to stop. See Voice orders.
- The placeholder reminds you: Hold space to speak · @ to direct. On an empty board it suggests asking what can you do?.
Aim an order with @#
- Typing
@opens a Direct to menu: everyone, then each console, then each group. Choose with Up and Down, accept with Tab or Return, dismiss with Esc. @Otto run the testsgoes to Otto only.@everyone,@alland@everybodyaddress every console. The mention itself is taken out of the text the agent receives.- A mention with nothing after it gets a nudge, such as Say what Otto should do.
- Names work without the @ too:
tell Otto to run the tests,Otto, run the tests,the backend group, run the migrations. When the planner is available, these forms go through it, and it writes the instruction. With an @ mention of one console your words are typed exactly; a mention of a group or of several consoles goes to the planner, which splits the work, and@everyoneworks like no mention. - When a name only sounds close, for example a spoken “Claudia” for your Claude console Otto, Symvibe holds the order and asks Did you mean Otto? With more matching consoles it asks whether to send it to all of them. Say confirm, or click Send.
The chips#
| Chip | What it does |
|---|---|
| New console | Starts one console: Claude, Codex, Gemini, Grok, OpenCode or an empty shell. |
| Spawn 4 | The group composer (name, role, one agent per slot) with four slots. |
| Group | The same composer with six slots. |
| Presets | The preset library. |
| Pause all, Resume all | Pause every console, or let them all continue. A paused console keeps its state. |
| Memory | The project memory panel. |
| Loops, Docs, Code, Skills, Mission Map | Shown while the thread is open. They open those panels. |
| Kill all | Shown while the thread is open. Two clicks, then a macOS confirmation, then every console closes. |
The thread#
- The chevron on the bar opens the thread: your orders, the replies, and a row for each agent's report.
- After each plan, a Plan note shows what each console was sent.
- When an agent you gave work to finishes, its row says it finished and how long it took, or that it failed and why, with the first lines of its reply and See output. Agents that do not answer within 30 minutes are dropped with a note.
- Ask
who finishedorwhat happenedfor where your latest order stands: who finished, who failed, who is still on it and who needs you.statuscounts what every console is doing and names who needs you. - The thread is kept per repo, up to the last 500 messages, in
~/Library/Application Support/Hypervibe/Threads. Clear empties it. The globe in its header sets the speech language.
What it understands#
Short, plain orders such as spawn 4 codex, pause Otto or open loops are understood on your Mac without the planner. They use no planner credits, but a spoken confirmation that is not cached yet does. If your speech language is set to one other than English, Spanish, Portuguese, French, German or Italian, every order goes to the planner. Whole sentences, questions and work for several agents go to Symvibe's planner service, which uses credits. Small talk such as “thanks” never reaches a console.
Voice and typed commands lists everything with example phrasings, and How orders reach your agents explains what happens next.
Keep going#
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.