Vnx Orchestration

VNX Orchestration

Governance-first runtime for AI coding agents

Glass-box governance · Multiple CLIs on subscription, not per-call API credit · Local NDJSON receipts

 
 
 

 
 

Docs · Architecture · State Fabric · ADRs · Writing · Changelog

VNX runs AI coding CLI workers in isolated git worktrees, through review gates, with an append-only NDJSON receipt per dispatch.

It is a local control plane for the AI coding CLIs that already sit on your machine. One orchestrator dispatches work to ephemeral workers; each worker runs in its own git worktree; review gates decide what merges; every dispatch leaves a receipt. VNX drives claude, codex, gemini, kimi, and local ollama with no vendor SDK. It calls the CLIs as subprocesses and never imports a provider library.

That has two distinct payoffs. First, governance: every dispatch is reconstructable, from what was assigned to what was reviewed to what merged and what each gate cost. Second, billing: because the workers are the CLIs themselves, the claude, codex and kimi lanes bill the subscriptions already on the machine, not per-call API credit. That is measured, not assumed: cost=$0.0000 receipts under a subscriptionType: max auth state (see "Billing follows auth, not the lane"). It does not hold for every lane. GLM, DeepSeek and any OpenRouter-routed model bill API credit, and only run where a project chose them or, for DeepSeek, as a review fallback when a subscription reviewer is unavailable (see "Multi-provider architecture" below).

Most agent projects build SDK-native agents. I orchestrate the binaries instead.

I built this for my own work, an estimated 3,000+ hours of development since February 2025. It is open source because the architecture is portable. Source is at…