SWE Forge turns explicit coding tickets into bounded, evidence-backed changes. It sits above your coding harness: it helps inspect, plan, implement, verify, review, and report without replacing the harness itself.
SWE Forge is Pi-first, with a portable canonical workflow and asymmetric harness adapters. It is opt-in, so ordinary harness prompts remain ordinary prompts.
ticket → inspect and plan → choose a topology → implement → verify and review → deliver/report
It chooses the smallest useful execution topology:
SOLOfor tightly coupled workSUBAGENTSwhen bounded delegation adds valueISOLATEDwhen concurrent writable work needs separate environments
Runs can work directly in one context, use subagents when available and useful, or use isolated writable workers when the host and provider can support them safely. The workflow specification and architecture guide describe the deeper behavior.
| Harness | Tier |
|---|---|
| Pi | First-class / reference |
| OpenCode | Compatible / secondary |
| Claude Code | Experimental |
| Codex | Experimental |
| Cursor | Experimental |
Support tiers and available capabilities are asymmetric; feature parity is not required. See the compatibility snapshot for current versions and validation evidence.
SWE Forge has no public release yet; the planned first alpha is
v0.1.0-alpha.1. Until publication, main is development-only. For
development, clone the repository into a stable user-level checkout and install
the harness projection as links:
git clone https://github.com/joacod/swe-forge.git ~/tools/swe-forge
cd ~/tools/swe-forge
scripts/swe-forge install pi
scripts/swe-forge verify piReplace pi with opencode, claude, codex, or cursor as needed. See the
installation guide for the supported link locations
and optional capabilities.
Invoke SWE Forge explicitly through the installed harness entry point:
/swe-forge <ticket>
The default GUIDED mode is reviewable and keeps you in the loop. Use PR mode
for the lower-touch path through pull-request creation:
/swe-forge pr <ticket>
Neither mode merges automatically. When needed, request the isolated topology explicitly:
/swe-forge isolated <ticket>
Codex exposes the same explicit skill as $swe-forge; the other listed
adapters use /swe-forge.
- Workflow specification
- Installation
- Architecture
- Harness compatibility
- Adapter documentation
- Contributing
SWE Forge is pre-alpha. For feedback, open an issue.