Browse / Software development / ForgeDock
ForgeDock
RapierCraftStudios
ForgeDock — autonomous AI dev pipeline for Claude Code.
Open RapierCraftStudios/ForgeDock → Does not match the four rules.
agent-memoryagentic-aiai-agentsai-code-reviewai-pipelineanthropicautonomous-agentsautonomous-codingci-cdclaudeclaude-aiclaude-code
Works with any agent
ships AGENTS.md, the cross-tool instruction file.
In its own words
GitHub as agent memory: issue in, PR out.
Point it at an issue and get a merged, reviewed PR; point it at a milestone and get parallel pipelines with conflict-aware scheduling.
LLMs generate the code. ForgeDock owns everything else — state, scheduling, recovery, review, and memory — as durable, inspectable structure on the GitHub you already have. Issues are the queue. PRs are the ledger. Annotations are the memory. Deterministic orchestration for autonomous software engineering.
ForgeDock (not ForgeRock) — this project is unrelated to ForgeRock's identity and access management platform.
📖 Full documentation site
One /orchestrate runs a whole milestone. Agents pick up issues in parallel, drive each through investigate → build → review, and flip the GitHub labels to merged — live.
This repository builds itself with ForgeDock. In its first 30 days (June 4 → July 4, 2026): 693 issues filed, 605 closed, 603 PRs merged — median 56 minutes from open to merged-and-closed. 57% of those issues were filed by the pipeline itself; 49% are findings its own review agents raised, filed, and then fixed. Every run leaves a public audit trail — click through the receipts, or count them yourself:
A single run, up close — a real one, issue #1230:
Try it in 30 seconds — on a throwaway repo, nothing to lose
Requires for this demo: Claude Code (subscription or ANTHROPIC_API_KEY) · GitHub CLI (authenticated) · Node.js ≥ 18.
The repository's own description, then 9% of its README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.