Vibestrate docs
Local-first orchestration for the coding agents you already use. A supervised plan → build → review → verify loop in isolated git worktrees.
Vibestrate runs software tasks through the coding-agent CLIs you already have on your machine - Claude Code, Codex, Aider, Ollama, OpenCode - and keeps every turn inspectable. It creates a git worktree, streams the agent’s output, runs your project’s validation commands, records artifacts, and stops at merge_ready, blocked, or failed. It does not push and does not merge for you.
Think of it as the missing supervisor for vibe-coding. You define the flow - plan with one model, implement with another, review with a third - and Vibestrate runs each phase under one visible, auditable process.
Reading paths
Get started in 5 minutes Install, configure a provider, run your first task.
Understand the concepts Tasks, agents, providers, Flows, skills, worktrees - what each one is, and why it exists.
Inspect the reference Every CLI command, every config key, every built-in Flow - generated from source.
Extend Vibestrate Add skills, providers, or your own Flow.
What Vibestrate is
- Local-first. No cloud backend, no hosted relay. Vibestrate never sends your code to its own infrastructure - the only network calls are the ones your provider CLIs already make.
- Provider-agnostic. Any local CLI that can take a prompt on stdin and produce a diff can be wired in. Claude Code is preset-ready; Codex, Aider, Ollama, and OpenCode are detected and configurable.
- Worktree-isolated. Every run gets its own git worktree. The orchestrator never edits your project root.
- Inspectable. Every prompt, output, metric, event, and approval is recorded under
.vibestrate/runs/<runId>/. You can read, replay, or audit any past run. - Human-gated. Reviews, approvals, merges - anything that affects shared state - is always explicit. No auto-push, no auto-merge.
What it is not
- Not a chat UI. Vibestrate is a workflow engine. The terminal and dashboard are surfaces for inspecting and steering it.
- Not a hosted service. There is no cloud SaaS edition.
- Not a model. Vibestrate doesn’t ship a model. It orchestrates the ones you choose to run locally.
A typical run, in one sentence
You write vibe run "Add audit logging to the settings flow", Vibestrate creates a worktree, the planner agent writes a plan, the executor edits files, the validator runs your tests, the reviewer reads the diff, the verifier confirms the result, and you decide whether to merge.
That’s the loop. Everything in these docs is detail on top of it.
