Launch day is when the site copy, the pricing page, the API fix and the release notes all move at once. Overvibe files every session under its project, colours the ones waiting on you amber, and turns their questions into a dialog you answer with a click.

On a busy day, the slow part is noticing. An agent stops to ask which plan the pricing section should lead with, and that question sits in a tab you haven't opened since lunch.
⌥N, pick the folder and the tool, and the sidebar files it under its project.
Teal is busy, grey is done, amber is waiting for you.
When a session shows a choice menu, it opens as a dialog over the page.
A coordinator session asks the others with overvibe send and writes the summary.
Behind it, a status check. overvibe ls gives an agent or a script the same view you get in the sidebar. Read the CLI reference
$ overvibe ls # each session: status (busy, idle, needs you), tool, folder $ overvibe send "web: release notes" "One line: what is left before we ship?"
Your computer and your plans set it. Each one is a normal CLI process in tmux.
Everything keeps running on Overvibe's own tmux server. Open the page again and the sessions are all there.
Yes. Give a folder its own Claude account in Settings, or pass --account when you start a session.
Claude drafts the advertorial, Codex goes after the hook and every claim, and you choose which version goes live.
From your phoneEvery Claude session starts with Remote Control on. From the Claude app, ask your coordinator which sessions need you.
Parallel features in worktreesTwo or three helpers build separate features at once, each in its own git worktree and branch, merged when they're done.
Install Overvibe, open a session for each job, and let the sidebar show you where to look.
