Coding & Development✨gemini🤖claude🌐universal
VNX Orchestration
Governance-first orchestration for Claude Code, Codex, and Gemini CLI — parallel workers, receipts, quality gates, and full provenance.
Quick Start
Install this Skill
npx skills add Vinix24/vnx-orchestration<div align="center"> # VNX Orchestration ### Governance-first runtime for AI coding agents **Glass-box governance · Multiple CLIs on subscription, not per-call API credit · Local NDJSON receipts** [](https://pypi.org/project/vnx-orchestration/)  [](LICENSE) [](https://github.com/Vinix24/vnx-orchestration/actions) [](https://github.com/Vinix24/vnx-orchestration/stargazers)   **[Docs](docs/) · [Architecture](docs/core/00_VNX_ARCHITECTURE.md) · [State Fabric](docs/core/STATE_FABRIC.md) · [ADRs](docs/governance/decisions/) · [Writing](https://vincentvandeth.nl) · [Changelog](CHANGELOG.md)** </div> --- 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 as a fallback when the subscription reviewers are 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 [github.com/Vinix24/vnx-orchestration](https://github.com/Vinix24/vnx-orchestration). This is not a security sandbox; it isolates work with git worktrees. It is not compliance certification; it produces a local, append-only, inspectable audit trail. It is optimized for human-gated coding workflows, not fully autonomous merges. ## What's new in 1.6 Seven releases on the 1.6 line so far (1.6.0 through 1.6.6, August 20 to September 27, 2026), all documented in the [CHANGELOG](CHANGELOG.md). The headlines: - **The review stack picks a subscription reader first** (1.6.6, #1928): the default is `codex_gate,kimi_gate`; `glm_gate` (OpenRouter credit) and `deepseek_gate` (own key) run only as a takeover-chain fallback when both subscription reviewers are unavailable. - **Gemini is retired as a reviewer** (1.6.6, #1932, #1934, #1935, #1936): the name is refused everywhere a review gate is selected, in defaults, profiles, enforcement YAML, the dashboard toggle and the docs. An existing `gemini_review` result in history still reads as a verdict, and the gemini CLI stays in use as a worker lane, just not as a reviewer. - **A partial read no longer books a pass** (1.6.6, OI-1851, #1920, #1937): a PASS on a diff a harness-lane gate could not fully read is `partial_review`, not a pass, and the merge door refuses it. Each harness-lane gate also got its own diff-char cap instead of one shared constant (kimi 400,000; glm and deepseek 50,000). - **T0 context rotation is enforced, not just recommended** (1.6.6, #1923): crossing 500K tokens in a T0 session now blocks new work until rotation runs. - **Build workers default to sonnet, T0 is pinned to Opus 5.5** (1.6.3, #1890): a claude-lane build-worker dispatch with no explicit model resolves to sonnet; before it resolved to kimi-k3 and was rejected. The pin is a default a dispatch spec can override, not a hard lock. - **Branch protection strictness is set per project** (1.6.5, OI-1849, #1917): `enforce`, `warn` or `off` in `branch_protection.yaml`, with the CI check as the floor under every setting, and the merge door judges the repo it is merging into rather than the repo it is installed from. - **The interactive tmux dispatch lane was retired** (1.6.2, #1845; r ... (truncated)
Repository
62stars
8forks
Details
Related Skills
More coding & development skills you might like
Reticle
Coding & DevelopmentAI agents can generate code, but still struggle to understand what they build. Reticle brings Jev-style machine-native runtime perception to web & desktop applications.
🤖claude🌐universal
1.2k
190
View
agentscope-java
Coding & DevelopmentExpert Java developer skill for AgentScope Java framework - a reactive, message-driven multi-agent system built on Project Reactor. Use when working with reactive programming, LLM integration, agent orchestration, multi-agent systems, or when the user mentions AgentScope, ReActAgent, Mono/Flux, Project Reactor, or Java agent development. Specializes in non-blocking code, tool integration, hooks, pipelines, and production-ready agent applications.
🌐universal
6.0k
1.5k
View
ospec
Coding & DevelopmentDocument-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
✨gemini🤖claude💬gpt🌐universal
524
34
View
misakanet-failure-memory
Coding & Development📚 A zero-dependency, git-backed micro-lesson library for AI Agents to asynchronously share and search verified debugging experience. Python stdlib only. | https://misakanet.org
🤖claude⌨️cursor🌐universal
424
158
View