Skip to content

ForgeFlow v2.0.0

Choose a tag to compare

View all tags
@BakerSean168 BakerSean168 released this 10 Sep 05:52
· 188 commits to main since this release
v2.0.0
a8242d9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ForgeFlow v2.0.0

ForgeFlow v2 is a breaking rebuild of the project around one principle: ForgeFlow governs software-engineering quality; Open SWE owns autonomous execution.

Highlights

  • Replaced the legacy Node/SQLite autonomous control plane with a small Python 3.14 policy graph running beside pinned Open SWE in LangGraph.
  • Added evidence-owned completion: an agent run reporting success cannot advance work without authoritative PR/head evidence.
  • Added exact-head CI and Official Open SWE Reviewer gates before READY.
  • Added bounded P0/P1/P2 repair loops that reuse the implementation thread and require provenance on repair commits.
  • Added a self-hosted Docker execution plane for Open SWE on GCP Dev with non-root execution, read-only rootfs, explicit noexec tmpfs mounts, AppArmor/seccomp/no-new-privileges, resource limits, private-network/metadata blocking, and provider-owned GC.
  • Added least-privilege GitHub App credentials: reviewer/dependency access is read-only; implementation write access is scoped to the primary repository.
  • Added persistent sandbox workspace/cache/artifact support, Python 3.14 + uv provisioning, safe reconnect/replacement after GC, and workflow-push handling for non-default base branches.
  • Removed OpenHands/Antigravity/legacy TypeScript execution ownership from the current runtime. Remaining OpenHands references are migration history, purge guards, or regression tests only.
  • Reworked README and docs/ to describe the implemented v2 architecture rather than the retired runtime or an aspirational design.

Acceptance evidence

The v2 policy path was exercised end-to-end on a real GitHub PR. A controlled regression removed the Docker read-only-rootfs boundary while deterministic CI still passed; the Official Reviewer raised a blocking high-severity finding, ForgeFlow entered REPAIRING, Luna xhigh repaired the issue on the same implementation thread, exact-head CI passed, the Official Reviewer resolved the finding on re-review, and the policy returned to READY with repair_round=1.

Additional real-project validation on Digital Biome exercised Open SWE implementation/reviewer sandboxes, private submodule hydration, exact-head CI, review findings, repair, and re-review.

Breaking changes

  • The v1 autonomous runtime, SQLite workflow state, legacy API/client compatibility surface, OpenHands execution plane, and old systemd topology are not migrated.
  • Git/GitHub/Open SWE/LangGraph are the source of truth for v2 work and durable execution state.
  • Existing v1 runtime state should not be restored into v2.

Runtime

  • Python 3.14
  • Open SWE pinned to 0ff86e22a94cc84e32883fcb1beee568560d4140
  • LangGraph deployment with agent, reviewer, analyzer, chat, scheduler, and forgeflow graphs
  • Self-hosted Docker sandbox provider on GCP Dev

See README.md and docs/README.md for the current architecture and operational documentation.

Assets 2
Loading