forge-ui

Stage: Public preview. forge-ui is public: anyone may install and use it. Its maturity is below alpha (pre-alpha): no SLA, and interfaces may change without notice.

Full visual platform for multi-tool AI orchestration.

This is L3: Ship Lord.

Sessions survive everything. Start a long-running task on your desktop. Close the browser tab. Open it on your phone during lunch. The session is still there, still running. Close your phone. Open your laptop at a coffee shop. Same session. Same progress. The Infinity Terminal is built on top of the orchestrator's file-based state layer. Session state is files. Files persist. Sessions persist.

That's the headline. Here's the rest: a real-time governance dashboard with health scores, a feed showing your tools coordinate in real-time, and a command center for executing Forge commands from the browser.

Install

git clone https://github.com/nxtg-ai/forge-ui
cd forge-ui
npm install
npm run dev

Requires the Forge Orchestrator (L2: Pro Builder) running in your project.

Sign-in and network access

The dashboard asks for this install's access token the first time you open it. On the machine running Forge:

npx tsx src/server/auth/print-auth-url.ts      # or: node dist/server/auth/print-auth-url.js

Open the link it prints. The token is created on first run at ~/.config/nxtg-forge/ui-secret (mode 0600); you can also paste it into the sign-in screen. Tools can send it as Authorization: Bearer <token>.

The dashboard (5050) and API server (5051) listen on 127.0.0.1 only. To open the dashboard from another device, set FORGE_UI_HOST=0.0.0.0 (both servers bind to it, and the API prints a warning) and add the device-facing origin to ALLOWED_ORIGINS, e.g. ALLOWED_ORIGINS=http://192.168.1.206:5050. Every request still needs the token.

The Infinity Terminal

The Infinity Terminal changes how you work with AI tools. Tasks that take hours aren't tied to a terminal window. You start them and walk away. Check in from any device. Pick up where you left off.

There is no socket connection to maintain. No server process that needs to stay alive. The terminal reconnects to state, not to a process. Network drops, browser restarts, device switches. It doesn't matter. The session is the state, and the state is files.

Governance Dashboard

The dashboard shows your project's health at a glance. Health score from A through F, computed across 8 quality dimensions: test coverage, documentation, security, code style, dependency health, API consistency, error handling, and type safety.

Trend monitoring tracks score changes over time and fires regression alerts. Tool orchestration shows which tools are active, which files are locked, and which tasks are in progress.

Governance state comes from the Rust orchestrator. The UI reads and displays it. Policy decisions are made in the core, not in the frontend.

Tool Activity Feed

Watch Claude Code, Codex CLI, and Gemini CLI coordinate in real-time. A tool claiming a task and starting implementation. The guardian agent running quality checks on the output. The planner decomposing a feature into subtasks. A security scan flagging a dependency vulnerability.

The feed shows tool assignments, task progress, file lock acquisitions and releases, knowledge captures, and governance events.

What You Get

58 React components. 4,165 tests. 87% coverage.

Prerequisites

• Forge Orchestrator running in your project (forge init && forge status)
• Node.js 18+

Links

• Forge Product Page
• Forge Plugin (L1: Vibe Coder — start here if you're new)
• Forge Orchestrator (L2: Pro Builder)
• Documentation

License

Source available under the Functional Source License 1.1 (FSL-1.1-ALv2). Converts to Apache License 2.0 on 2028-03-18. See LICENSE.md.

Versions up to and including v3.1.2 were published under the MIT License; FSL-1.1-ALv2 applies from v3.1.3 onward.