OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Coding Agents

Forgedock

An open-source autonomous software-engineering pipeline for Claude Code that uses GitHub issues, pull requests and annotations to coordinate coding work, review, recovery and memory.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Forgedock — OpenViST project profile in Coding Agents.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use ForgeDock when software work is already organized in GitHub issues or milestones and you want Claude Code agents to handle more of the implementation and review flow.

Who it is for

  • Developers working from GitHub issues
  • Teams managing repository work through milestones
  • Users of Claude Code who want structured autonomous coding pipelines

Documented uses

  • Turn a GitHub issue into an investigated, built and reviewed pull request
  • Schedule parallel coding pipelines from a milestone
  • Preserve findings and pipeline state in GitHub for later agents and recovery
  • Record review results and follow-up work in inspectable repository artifacts
Before you choose

Requirements & limits

The repository is public and licensed under AGPL-3.0. The documented setup requires Claude Code, an authenticated GitHub CLI and Node.js 18 or later.

  • The primary workflow depends on GitHub as the issue, pull-request, annotation and recovery environment.
  • Claude Code is the documented coding-agent ecosystem.
  • Milestones support parallel pipelines with conflict-aware scheduling.
  • The project is JavaScript-based and released under AGPL-3.0.
  • Moving to another issue tracker or code host requires modification; compatibility is not demonstrated.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up ForgeDock for a repository

Prepare ForgeDock to inspect a repository and create its annotated configuration.

Before you start

  • Claude Code with a subscription or ANTHROPIC_API_KEY
  • Authenticated GitHub CLI
  • Node.js version 18 or later

Steps

  1. Run npx forgedock.

  2. Let the setup check the environment, install the slash commands and read the repository.

  3. Review the generated forge.yaml and confirm it once.

Expected outcome

ForgeDock produces an annotated forge.yaml for the repository and completes the documented setup flow.

Guide limitations

  • This guide documents setup only, not execution of a real coding task.
  • The documented workflow is built around GitHub and Claude Code.
Documentation 1 ↗
Source-based practical guide

Run the risk-free demonstration

See the ForgeDock pipeline operate in a throwaway repository.

Before you start

  • Claude Code with a subscription or ANTHROPIC_API_KEY
  • Authenticated GitHub CLI
  • Node.js version 18 or later

Steps

  1. Run npx forgedock demo.

  2. Allow the command to create the documented demo repository.

  3. Observe the pipeline end to end.

Expected outcome

The demo shows ForgeDock's pipeline in a risk-free repository.

Guide limitations

  • The demonstration is separate from configuring ForgeDock for a production repository.
  • The evidence does not document further demo controls or cleanup steps.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
30 September 2026
Original website title
RapierCraftStudios/ForgeDock · Official homepage title · retained in its source language
How we review sourcesSuggest a correction