Overview
VIDA is a voice-first orchestrator for development work. You talk to it; it keeps track of your backlog and everything in flight, hands work to Claude Code in isolated worktrees, and puts the decisions only a person can make in front of you.
Early development. VIDA runs today as one developer's assistant on their own workstation. Team installs and remote deployment are coming soon. This guide describes the shape of the product, not a stable interface.
The idea
Coding agents made writing a change cheap. They did not make it cheap to keep track of ten changes at once: which finished, which you have read, which are safe to merge, what you promised to look into. That bookkeeping lands on a person, and it is where work gets lost.
VIDA holds that state for you. It notices what is slipping, says so in a sentence, and shows the detail on screen. It never decides the things that should be yours: what lands, and what goes to main.
What it does
- Runs tasks in parallel. Each is a Claude Code session in a git worktree and branch of its own, started from a sentence or a tracker issue key, with a live feed of what it is doing.
- Waits for review. Finished work is done, not merged. It is listed under "needs review" until a person reads it in the review tab and says to land it.
- Lands on dev, promotes on your word. Everything lands on a dev branch as one revertible merge. Main moves only when a person explicitly says to promote.
- Works your tracker. Linear issues become briefs; issues move as their tasks do; an autopilot can work through a project's backlog under screens and a budget.
- Runs signed plans. Bigger changes go through SynthKit plans, signed in the HUD with your SSH key and run in dependency waves under a budget cap.
- Keeps the rest of the day. Reminders, your calendar, notes about how you like to work, and a summary of what happened while you were away.
What it is not
- Not a coding agent. The code is written by Claude Code. VIDA decides nothing about what lands.
- Not a replacement for review. It makes review the default instead of a race.
- Not tied to one model. The model that talks to you sits behind one adapter, and everything valuable lives outside it.
Where to go next
- Getting started: what it runs on and the first hour.
- The workflow: from a sentence to main, step by step.
- Concepts: tasks, landing, asides, the autopilot, plans and more.
- Use cases: what it sounds like in practice.