Local-first · Zero runtime dependencies · MIT

Orchestrate AI coding engines
with guardrails.

VibeFlow is a local-first CLI and web UI that drives Claude Code, Codex, and GitHub Copilot CLI as an orchestrator — with engine preflight, git source protection, work-unit orchestration, and verification built in.

npx @magicpro97/vibeflow

View on GitHub npm package

Watch the coordinator orchestrate

A real orchestration, start to finish: the engine plans a refactor, writes the code, and self-verifies — typecheck, lint, full test suite, and 100% per-file coverage — before an independent reviewer signs off. No completion without evidence.

What it does

Multi-engine, out of the box

Drive Claude Code, OpenAI Codex CLI, and GitHub Copilot CLI from one orchestrator with shared context and instruction files generated per engine.

Source protection

A git checkpoint before every real dispatch: clean-tree gate, opt-in --auto-wip snapshot, and one-command rollback so an engine run never loses your work.

Engine preflight

Probe each engine for presence, auth, and a live round-trip before dispatch. Workflows only start when an engine actually works — no silent dead ends.

Work-unit orchestration

Decompose a task into non-overlapping work units, dispatch them in parallel, and gate completion on a confidence check with recorded evidence.

Universal guardrails

Hooks score every action and block destructive commands, secret reads, and out-of-scope writes — natively on Claude, detection-only with a banner elsewhere.

Skills & code-nav tools

Capability-matched skills plus optional codegraph and LSP navigation, wired as MCP servers with a codegraph > lsp > native priority ladder.

How it works

vf init
Scan the repo and generate canonical context + per-engine instruction files.
vf doctor --probe
Confirm an engine is installed, authenticated, and responding before any work.
vf orchestrate --yes
Checkpoint the tree, dispatch work units in parallel, and review each result.
vf verify
Run typecheck / lint / test plus confidence, evidence, and scope gates.

Use VibeFlow as a skill

vf init seeds a vf skill into your repo and syncs it to Claude Code, Codex, and GitHub Copilot — one cross-engine skill, no per-tool wiring. Activate it by typing <your task> + vf in a prompt, or /vf in a CLI tool. Run /vf with no args and it grills you toward a spec from the chat context.

$ npx @magicpro97/vibeflow init
Seeding the `vf` skill → .claude / .codex / copilot…
  ✓ vf skill written and synced to every engine

# then, inside Claude Code / Codex / Copilot:
> Refactor the auth middleware + vf
> /vf            # no args → grills you toward a spec

Learn more in the Skills system reference.

From install to first check

$ npx @magicpro97/vibeflow doctor
VibeFlow environment check

  ✓ node
  ✓ git
  ✓ claude
  • codex (optional)
  ✓ copilot

  git repo: yes

Engine readiness (presence/auth):
  ✓ claude: installed
  ✓ copilot: installed

Ready.

Orchestrate AI coding engineswith guardrails.