Verbative

Command a team

One voice, a whole team. Below the voice layer, Verbative is a multi-channel Agentic Development Environment— group your Claude Code sessions, run several agents in parallel, put every idea in front of an automatic design-review panel, and let the agents keep a living Spec → Build → Review → Ship board as they work.

Channels — parallel agents

A channel groups one or more Claude sessions — called agents— that run at the same time. Use a channel per project, feature, or area, and add as many agents inside it as you need; each agent is its own live claude session in its own VS Code terminal. In the Verbative panel you pick the active channel and agent, and your dictation and the voice key are routed there— switching focus to another agent is a single click. Add a channel or an agent, rename them, and start fresh, resume, or continue any session right from the panel.

When more than one agent is live, Verbative keeps every voice legible. The panel marks the agent that currently has your voice with a 🎙 your voice badge, and each agent announces its channel and name before it speaks (e.g. “Web App, Checkout flow: …”) so you always know who's talking. Every agent's spoken output flows into the one voice queue, each cue tagged with its agent, and a busy agent's row animates so you can see at a glance which agents are working. Each agent also has its own mute, working-pulse, and attention-beeptoggles — silence or tune one agent without touching the others, while the global working-pulse and attention-beep toggles in the Channels header stay the master switches over all of them.

Every channel also keeps a shared memory: a notes file that's woven into each agent's prompt. Jot a decision, file change, or convention there — or ask an agent to — and every other agent in the channel sees it on its next turn, so they stay coordinated without you re-explaining context to each one. The whole layout persists per project in .verbative/workspaces.json (and the shared notes under .verbative/workspaces/). Available on every plan: Free includes 1 channel with up to 2 parallel agents; Advanced is unlimited.

Verbative
Web App · Onboarding
Idle — waiting for voice command
Speed 1.3×
Channels
Web App
🧠 Shared memory
Checkout flowOpus 4.8
effort
Onboarding🎙 your voiceOpus 4.8
high
+ Add an agent
Payments API
🧠 Shared memory
Stripe webhooksOpus 4.8
effort
+ Add an agent
+ New channel

Each channel runs its own Claude agents in parallel. Your voice goes to the selected agent.

ProblemsOutputTerminalPorts2 splits
build the checkout payment flow
Wired up the Stripe PaymentIntent with an idempotency key and the charge path.
Ran 1 shell command
All 18 tests pass. Edited src/checkout/intent.ts (+24 −3).
Reading 1 file, running 1 shell command…
src/checkout/intent.ts
add a 3-D Secure fallback
Web App · Checkout flow
1h12m · 184.6k tok (41%)
finish the onboarding welcome step
Built the welcome step and added form validation.
Ran 1 shell command
Edited src/onboarding/Welcome.tsx (+41 −8) — awaiting review.
Composing… (47s · still thinking)
Web App · Onboarding
47m18s · 92.3k tok (22%)

One window: the Verbative panel on the left, each agent's live terminal on the right. Every agent carries a status bar right inside its split — channel, agent, time, tokens, and context used.

See Channels in action →

Advisory Board

A standing design-review panel for every prompt. Turn it on and each prompt is reviewed in parallel by six domain advisors — Backend, Frontend, Security & Compliance, QA, Product, and DevOps / SRE — each running on Haiku in its own neural voice. An advisor only speaks when the concern is in its lane (out-of-lane piling-on is forbidden); their findings are handed to your Tech Lead (your normal Claude Code session), which writes the code. The same panel then reviews the result and forces at most one revision — bounded, with no infinite back-and-forth.

The board is yours: activate or deactivate any advisor, or add your own with its own name, focus, and voice (click any advisor to read, read-only, the exact instructions it's given). Toggle it in the Verbative panel or say “advisory board” by voice; “repeat review” replays the last batch. Free includes up to 10 reviews a day; Advanced is unlimited.

Your prompt
  • { }
    Backend
  • <>
    Frontend
  • Security
  • ✓✗
    QA
  • Product
  • DevOps
Tech Lead — writes the code

Each advisor · Haiku · its own voice

Every prompt fans out to the panel; the Tech Lead synthesizes their advice and writes the code.

See the Advisory Board in action →

Project Roadmap

Hands-free, you lose the screen — so you lose the thread of what's done and what's next. Project Roadmap is a live map of your project plus a Spec → Build → Review → Ship board that Claude keeps in sync as it works. Each card carries its own git lifecycle: a branch when work starts, WIP commits as it builds, a diff to review, and a merge + tag when it ships — so the board and your repo never drift apart.

Open the board from the panel, or say “project roadmap”by voice to toggle it; as Claude updates it, Verbative speaks each milestone aloud (“Updating the roadmap.” … “Roadmap updated.”) so you stay oriented without looking. It lives under .verbative/ in your repo — kept on your machine (Verbative gitignores it by default), so a fresh session — or a fresh you, after a walk — picks up with the full picture instead of a cold start. Free includes up to 10 board updates a day; Advanced is unlimited.

Project maparchitecture, kept live
FRONTENDBACKENDcallsverifiesreads / writesguardsemitsWeb appAPI gatewayRate-limiterMagic-link authPostgresWebhooks
Kanban boardSpec → Build → Review → Ship
Spec1/4
Magic-link auth
Export to CSV
{ }Build2/4
Rate-limit middleware
Magic-link auth
feat/magic-link · 3 commits
Review3/4
Webhook retries
✓ Approve✗ Reject
Ship4/4
Onboarding email
Dark mode

A card rides Spec → Build → Review → Ship; Claude moves it and drives the git lifecycle as it works.

See the Project Roadmap in action →