Skip to content

AI coding workflow

SWE Forge

One ticket. Validated changes. Readable commits. One reviewable PR.

View on GitHubOpen source · MIT

A Git-native workflow layer, not another agent

SWE Forge is a portable, opt-in, Git-native workflow layer for the coding agent you already use. It inspects the repository, chooses the smallest useful execution setup, implements and validates cohesive slices, runs a fresh independent review, and delivers one inspectable PR with a readable commit history. It never merges for you.

A consistent path from ticket to reviewable Git artifact, with validation built in. It never merges for you.

Start here

Install it where you work.

This installs the Pi bridge globally. OpenCode, Claude Code, Codex, and Cursor also support project-local or global installation; use opencode, claude, codex, or cursor as the harness name and --target /path/to/project for a project install. Install one harness at a time. For project installs, link mode follows this checkout by default; --mode copy creates a reviewed snapshot.

git clone https://github.com/joacod/swe-forge.git ~/tools/swe-forge
cd ~/tools/swe-forge
scripts/swe-forge install pi --global
scripts/swe-forge verify pi --global

Use it

Start one ticket at a time

Installation only makes the workflow available; it does not change ordinary prompts. Activate it explicitly for one ticket with /swe-forge in Pi, OpenCode, Claude Code, or Cursor, and $swe-forge in Codex. Start with:

/swe-forge add a loading state to the dashboard
/swe-forge solo fix the failing parser test
$swe-forge review the authentication change

What stays simple

  • Opt in per ticket instead of turning every task into a ceremony.
  • Use the smallest execution mode that can solve the work reliably.
  • Make validation and fresh review part of delivery, not an afterthought.
  • Keep commits, pushes, pull requests, merges, and other external effects explicitly authorized.