drove
one autonomous, local pipeline

Claude plans. Codex builds. OpenCode reviews.

Use the CLIs and subscriptions you already have. Drove runs them locally, then hands you a reviewed branch and checks.

Run Drove locallyHow it works

Do not ask the writer to grade its own work.

Drove hands the finished diff and task to a fresh reviewer. You get the review, test output, and cost with the branch.

Independent review

Use a different model for the review, or clearly see when the same one was used.

Isolated worktrees

Your own checkout stays untouched while each feature runs in its own Git worktree.

Evidence, not a thumbs-up

Read the diff, reviewer notes, command output, and cost before you decide to merge.

Choose who does each job.

Mix the coding CLIs already on your machine. For example: Claude plans, Codex writes, and OpenCode reviews the finished diff.

Change the CLI and model for Plan, Build, and Review in Stages. Leave a model blank to use that CLI's default.
Stages · my workspaceSave
PlanReads code and writes the plan.
Claudedefault
BuildWrites on an isolated branch.
Codexdefault
ReviewJudges the finished diff.
OpenCodedefault

Independent review: Drove warns you if Build and Review use the same CLI.

Start local. Stay in control.

Install Drove once, add an existing Git repository, then approve your first plan.

# install once
uv tool install git+https://github.com/depak7/drove
drove serve   # http://localhost:8787

Clear limits. No surprises.

  • You choose what to build. A review can catch code mistakes, not a bad product decision.
  • Drove uses existing Git repositories. It pushes branches and compare links; you open and merge the PR.
  • It uses your own model subscriptions and records each run's cost.