Public preview: free to install. The plugin is open source (MIT) and the orchestrator is source-available (FSL-1.1). Alpha testing is in progress, and interfaces may change.
AI Development Orchestration
Multi-agent isn't the problem. Multi-tool is.
Inside a single environment like Claude Code, agents coordinate fine. They share orchestration and context. The trouble starts when you run multiple AI tools on the same repo. Claude Code for refactors. Codex CLI for tests. Gemini CLI for research. Each tool operating with its own memory, its own assumptions, and no shared state.
NXTG-Forge solves this with a Rust binary, MCP protocol, and a shared .forge/ state directory.
File Locking at the Rust Level
When one tool starts editing a file, Forge acquires an exclusive lock. Other tools queue until the lock is released. This runs in the 6.4 MB Rust binary at the core of Forge. The core has 572 Rust tests. Lock timeouts and deadlock detection are in progress (build B4, target 2026-10-20). Not a suggestion. An enforcement mechanism.
Shared State Through MCP Protocol
The gap between AI tools isn't capability. It's awareness. Each tool is individually capable. None of them know about each other.
Forge exposes 11 MCP tools that any connected AI tool can access. Task status, file locks, knowledge entries, and governance state are all available through standard MCP calls.
Claude Code communicates via MCP stdio. Codex CLI, run as a task runner, uses filesystem conventions. Gemini CLI support is in development (build B1, target 2026-10-27). Both read from and write to the same .forge/ directory. Each tool reads its native config format. No wrappers. No Forge-specific configuration language.
Knowledge That Compounds Across Tools
Decisions made during a Claude Code session get captured in .forge/knowledge/. When Codex CLI starts a session the next day, those decisions are available. The knowledge flywheel works across tools, not just within a single tool's session history.
Task Board With Dependency Awareness
Instead of manually coordinating which tool does what, Forge maintains a task board with dependency graphs. Tools check which tasks are available, claim work, and report progress. The orchestrator tracks dependencies and prevents tools from starting blocked tasks.
Drift Detection
You wrote a spec. A tool started working. Is it still following the spec? Forge compares in-progress work against the original plan and flags divergence before it becomes expensive to fix. Drift detection needs a configured model.