commonforge-org/commonforge is a self-hosted platform where multiple agents and people modify one project together, running on Cloudflare Workers and Artifacts. The commit 686b9cc of October 17, 2026 merged PR #1 of the PublicRepo-Implementation branch, adding the implementation for a public repository. The diff stat is 9,830 insertions and 64 deletions.
The center of this commit is the procedure for handing the project's criteria over to agents. The CLI gained the commands `cforge handoff`, `cforge checkout`, `cforge context`, `cforge submit`, `cforge propose`, `cforge results`, `cforge renew`, and the checked-out working folder receives the protected files `.commonforge/context.json` and `.md`, which contain rules, action scenarios, assignments, and context digests. Submissions reject stale context, and results distinguish currently valid evidence from superseded runs and failures. Renewal revokes the previous task's permissions and pins new context, leaving past workspaces behind as history. The same capability is also provided as a structured MCP (a protocol by which agents call external tools according to a defined specification) equivalent, and under task permissions it is impossible to finalize rules, approve, deploy, or access other tasks.
The README calls this flow a 'limited G1 workflow' and states that it has been validated through actual local execution, handoff to a new agent, and a rehearsal of isolated Cloudflare deployment, expiration, and recovery. The validation is handled by the new `g1-local` job in CI (G1 real Git, runner and owner browser journey). It finishes within 15 minutes on ubuntu-latest; it installs bubblewrap, relaxes AppArmor's unprivileged userns restriction, and then verifies the browser path with Playwright's Chromium. Run artifacts and screenshots are kept for 7 days, while the original run evidence is blocked with gitignore and only reviewed summaries are published to `docs/agent-native/evidence/`.
However, the README itself bounds the scope of the validation. Production native deployment and complete Git bundle restoration still have additional requirements outstanding, and only new web projects have this workflow as the default; existing legacy projects require explicit activation. The CLI documentation also states that `cforge propose` can report a merge-pending state, and that cases where execution is impossible are not counted as successful behavior verification. Since this is the first implementation for a public repository and the validation scope is explicitly stated as G1, it is currently close to the stage where it should be kept as a reference implementation and the results observed.