This release is a pre-release and may not be stable for production use.
Forge
Forge is an open-source, CLI-first multi-agent orchestration framework for autonomous, auditable software development. Designed for software engineers and development teams who want to incorporate AI coding agents into real codebases safely, Forge eliminates the risks of unconstrained single-model generation—such as silent bugs, architectural drift, and unverifiable claims—by organizing specialized local CLI agents into a disciplined engineering pipeline with strict separation of concerns, empirical runtime testing, adversarial diff-first review, and complete human-in-the-loop oversight.
Features
- Multi-Role Engineering Pipeline: Coordinates specialized roles in an auditable sequence: Critic (
00), Architect (01), Planner (02), Executor (03), Tester (04), Reviewer (05), and post-execution Critic (06). - CLI-Native Agent Invocation: Operates directly through installed developer CLI binaries (OpenCode, Google Antigravity /
agy, and OpenAI Codex) as subprocesses without proprietary cloud API wrappers or token markups. - Empirical Black-Box Testing: Evaluates running applications through real interfaces (Headless Chromium via Playwright, REST/GraphQL APIs, CLI binaries, Library imports) under process group supervision (
RuntimeSupervisor), collecting viewport screenshots, telemetry logs, and executable reproduction scripts. - Diff-First Adversarial Review: Change-centric quality gate where the Git diff is the primary review artifact. The Reviewer validates Executor claims against actual codebase changes and empirical test evidence before granting approval.
- Autonomous Self-Repair Loop: In
forge auto, automatically iterates between the Executor, Tester, and Reviewer. If tests fail or changes are requested, structured issue feedback is fed back into subsequent implementation attempts until approved or retry limits are reached. - Interactive Checkpoints & Resumption: Run interactively with step-by-step confirmation checkpoints (
forge run) or resume any previous run seamlessly (--run run-XXX), automatically skipping already completed stages. - Project Knowledge Base (PKB): Automatically discovers and tracks persistent repository knowledge across runs in
.forge/knowledge/(architecture.yaml,features.yaml,decisions.yaml,unresolved.yaml) with role-based permissions and human locking. - Terminal User Interface Dashboard: Interactive terminal dashboard (
forge dashboard) to monitor live runs or inspect historical runs with timeline navigation, streaming console output, stage artifacts, test evidence, and knowledge base browser. - Git Safety & Change Attribution: Captures unified diffs with automatic filtering of
.forge/runtime data and.env*secrets, intelligently attributing changes to avoid committing mixed-ownership files containing pre-existing user edits. - Process-Level Run Locking: Kernel-backed exclusive run locking (
flock) prevents concurrent process conflicts on the same run directory with automatic stale-lock recovery.
Requirements
- Python:
>= 3.10 - Git:
>= 2.25installed and available inPATH - Supported Agent CLIs (at least one installed and authenticated):
- OpenCode (
opencode) - Google Antigravity (
agyorantigravity) - OpenAI Codex (
codex)
- OpenCode (
- Optional for Web Testing:
playwright(pip install playwright && playwright install chromium)
Platform Support
Forge is primarily developed and tested on Linux. For Windows users, WSL2 is the recommended environment.
| Platform | Status | Notes |
|---|---|---|
| Linux | Supported | Primary development and testing platform. |
| WSL2 | Supported (Recommended for Windows) | Full compatibility with all pipeline stages and process supervision. Note: CLI agent tools (e.g. OpenCode) must also be installed natively inside the WSL2 Linux environment; Windows host binaries exposed via WSL PATH are not supported. |
| macOS | Supported | Compatible with POSIX process isolation and standard pipeline execution. |
| Native Windows | Not Supported | Forge relies on Linux/WSL-compatible process management for runtime supervision and testing. |
Installation
Install Forge from PyPI:
pip install forge-orchestrator
Development Installation
To contribute to Forge or install directly from the source repository:
git clone https://github.com/Mathir14/Forge.git
cd Forge
pip install -e ".[dev]"
Verify your installation:
forge --version
forge doctor
Quick Start
Get started with Forge in under 5 minutes:
# 1. Initialize Forge prompt templates and configuration in your project
forge init
# 2. Check installed CLI tools, git state, and stage configurations
forge doctor
# 3. Perform a standalone codebase audit for technical debt and vulnerabilities
forge critic "Audit authentication system and error handling"
# 4. Implement a task with step-by-step confirmation checkpoints
forge run "Add /healthz JSON endpoint with uptime and git commit SHA"
# 5. Inspect the execution artifacts and timeline in the interactive dashboard
forge dashboard
To run the pipeline completely unattended with autonomous self-repair:
forge auto "Implement rate limiting middleware using token bucket algorithm" --auto-commit
Supported Adapters
Forge connects to installed CLI tools using native adapters. View all registered adapters and their capabilities at any time using forge adapters:
| Adapter | Binary | Default Model | Prompt Transport | Core Capabilities |
|---|---|---|---|---|
opencode |
opencode |
Provider default | stdin |
code_read, code_edit, shell, git, structured_output, custom_flags |
antigravity (agy) |
agy or antigravity |
gemini-3.7-flash-high |
-p flag |
code_read, code_edit, shell, git, long_running, structured_output, custom_flags |
codex |
codex |
gpt-5.6-terra |
stdin (-) |
code_read, code_edit, shell, git, long_running, structured_output, tool_calling, custom_flags |
Documentation
For full operational details, configuration schemas, CLI command reference, testing engine guides, and troubleshooting workflows, consult the Complete User Guide.
Contributing
Contributions are welcome! Please read CONTRIBUTING.md for guidelines on development environment setup, coding conventions, and submitting pull requests.
License
Forge is licensed under the MIT License.
Metadata
Release files for forge-orchestrator 0.1.0b5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| forge_orchestrator-0.1.0b5.tar.gz | 307.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| forge_orchestrator-0.1.0b5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 484.6 kB
Release files / forge_orchestrator-0.1.0b5.tar.gz
| Download URL | forge_orchestrator-0.1.0b5.tar.gz |
|---|---|
| Size | 307.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b595f44931cefef2df5ece87b0fde87cf47e7a7e469dc68f27fc6ca9fa8809d
|
|
BLAKE2b-256 checksum How to use checksums |
122a2376e268f99bebce08083677af52cdfa92b76cba9dfc6d3b4352f18ebb64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logRelease files / forge_orchestrator-0.1.0b5-py3-none-any.whl
| Download URL | forge_orchestrator-0.1.0b5-py3-none-any.whl |
|---|---|
| Size | 176.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fafbb9e6fbe984dbd76f243f4ecbf8936ec81b5475de1701599c0c5b41101213
|
|
BLAKE2b-256 checksum How to use checksums |
61abe618c6b9512c6e1252409bfb43e3e86f8f914fa87239b9dd8ae5f0b5a264
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency log