forgedock

Why ForgeDock

AI coding agents forget everything between sessions. They re-investigate the same bugs, miss context from past PRs, and make mistakes that were already caught and fixed last week. There's no institutional memory.

ForgeDock fixes this by using GitHub itself as the memory layer. Every pipeline stage writes structured FORGE: annotations to issues and PRs. Every downstream agent reads them. When a new session starts — even after Claude's context resets — the agent queries GitHub and picks up exactly where the last one left off.

---

How Is This Different

ForgeDock is not another AI coding agent. It's a set of prompt-engineered command specs (.md files) that run inside Claude Code. No new runtime, no separate process, no vendor lock-in beyond what you already use.

	ForgeDock	Plain Claude Code	Cursor / Windsurf	Devin / Sweep
Memory across sessions	Structured annotations on GitHub	CLAUDE.md + manual notes	Per-project context	Proprietary cloud state
Autonomous pipeline	Full lifecycle: investigate → merge	Manual, step by step	Autocomplete + chat	Autonomous but opaque
Review quality	9 domain-specialist agents	You review everything	Basic suggestions	Varies
Infrastructure needed	None — just npx forgedock	None	IDE-specific	Cloud service
Codebase visibility	Everything stays on GitHub	Local	Local + cloud sync	Cloud-only

---

What You Get

Capability	How it works
Full-lifecycle automation	/work-on #42 — investigates the issue, architects a fix, builds it, runs quality gates, opens a PR, and reviews it. You click merge.
Persistent agent memory	Structured FORGE: annotations on GitHub issues/PRs survive context resets and session boundaries. Agents never start blind.
9 specialist review agents	Security, billing, database, concurrency, auth, frontend, API, performance, infrastructure — every PR gets domain-expert review.
Cross-issue knowledge graph	Agent fixing issue #43 reads the investigation from #42 and applies the known pattern — no re-investigation.
Self-improving pipeline	Review agents learn from past findings — recurring patterns automatically become new quality gate checks.
Parallel orchestration	/orchestrate decomposes milestones into waves and runs /work-on on each in parallel.

Cost note: ForgeDock itself is free and open-source. It orchestrates Claude Code sessions, so you pay your normal Anthropic API usage. A typical /work-on run on a straightforward bug uses roughly the same tokens as a 15–20 minute manual Claude Code session.

See a real pipeline run

Here's what a real run looks like on issue #619 — a performance bug where command specs were burning ~200K tokens in context: