DSH HUB
HomePlugin StorePlugin PacksCommunityRankingsResourcesPublish Guide
Plugin source
Back to catalog

Lijiajin95 /

Lijiajin95/ForgeLoop

Topic repository only

A DeepSeek Harness plugin for multi-agent software development and operations, with traceable delivery and human decisions for exceptions.

★ 0 Stars0 Forks0 IssuesN/A Community rating0 Confirmed installs
View on GitHub
READMESource: main@c2870857

ForgeLoop

English | 简体中文

Multi-agent software development and operations, built on DeepSeek Harness (DSH).

ForgeLoop aims to help people who need software but do not work in software engineering turn business goals into running applications. Customers define the goals and authorization boundaries; agents handle routine engineering and bring exceptions back for a human decision. Requirements, changes, verification results, and delivery evidence remain traceable throughout the process.

Early development. ForgeLoop has a native TypeScript plugin foundation. The complete autonomous development, deployment, and operations workflow is still being built and validated. Product goals are not claims of completed capability.

What ForgeLoop is building

  • A path from requirements to running software. Coordinate analysis, technical planning, implementation, independent verification, release, and checks in the running environment.
  • Clear customer decisions. Escalate conflicting goals, changes to authorization boundaries, major architecture changes, and other defined exceptions with evidence and understandable options.
  • Delivery you can inspect. Connect each requirement to its tasks, candidate changes, test results, review findings, and release artifacts.
  • Continuous improvement. Turn authorized operational feedback into recovery work and follow-up development requirements.

The intended workflow is:

Requirements → Analysis & planning → Implementation → Independent verification
             → Business acceptance → Deployment → Checks in the running environment

The first use case is ForgeLoop itself: build a usable seed, use it for real improvements, and measure how much external help each iteration requires. Development and operations are assessed separately; the long-term target is less than 10% human intervention in each, not a result already achieved.

Built for DeepSeek Harness

DSH is the only persistent host. It provides sessions, model access, tools, UI integration, and process lifecycle services. ForgeLoop adds the software delivery workflow and its business records.

Layer Responsibility
DSH host Sessions, models, tools, permissions, and plugin UI integration
ForgeLoop domain Requirements, task plans, authorization, failure accounting, and delivery rules
ForgeLoop runtime Durable coordination, Agent execution, workspaces, review, and formal test execution
Records and evidence SQLite business records; files for diffs, logs, reports, and candidate artifacts

The active implementation lives in packages/forgeloop. It uses TypeScript and Node's built-in SQLite support. ForgeLoop does not require a separate persistent backend.

The target design defines five identities: Product Agent, Orchestrator Agent, Development Agent, Verification Agent, and Operations Agent. The Orchestrator Agent only routes work: it reads a new requirement plus the existing development sessions and picks the session to run it in (creating one when none fits). Each development session keeps a fixed workspace, is never deleted on its own, and leaves a summary tied to its session id when a round ends; a requirement that targets a busy session waits for it instead of running in parallel. The Verification Agent runs independent verification and business review in one freshly opened session. These are in-process Agent sessions with runtime checks, not OS-level role isolation. See the architecture and product plan for the distinction.

A first-version Operations Agent is also in place: registered resource checks, a periodic active monitor that samples host CPU, memory and load, process aggregates, HTTP latency, log tails, alert files and the last result of every check, a small catalog of recovery actions, a tool-free review and diagnosis session, recovery actions executed only with catalog or owner authorization and re-checked afterwards, one best-effort webhook alert per new event, and linked fix requirements when a diagnosis calls for permanent repair. Actions run in the host account with no OS isolation, nothing is collected until ops.monitor is enabled, and online incidents have not been exercised yet — see the operations design.

Current foundation and priorities

The repository includes versioned requirements and task plans, development workspaces scoped to reusable dev sessions, orchestrator session routing, candidate diffs, independent verification and business review, formal test execution, durable requests, and evidence records; pre-implementation review, independent diff review, and approval/acceptance are kept only for historical compatibility. DSH tools and a web board expose project information.

Some workflow operations remain internal, and availability depends on the revision being used. A successful tool call, test run, or package installation does not by itself prove complete delivery. The status record documents implementation, actual validation, and known gaps.

Current priorities are:

  1. A usable DSH workbench: unified navigation, requirement and task details, execution activity, errors, and evidence for everyday use and debugging.
  2. Controlled execution: role permissions, reliable stopping and recovery, and consistent authorization and failure accounting at action boundaries.
  3. A verified delivery loop: carry the same candidate through verification, controlled deployment, and checks of the running version.
  4. Real self-improvement: record outcomes, failures, external intervention, and operational recovery before assessing autonomy.

Development

Use Node.js, npm, and a DSH version compatible with the workspace and plugin manifests. The first target environment is macOS.

git clone https://github.com/Lijiajin95/ForgeLoop.git
cd ForgeLoop
make setup       # Install dependencies
make check       # Full checks: type checking, contracts, all behavior tests
make check-fast  # Quick checks; never runs mutation testing
make check MUTATION=1  # Full checks plus full Stryker mutation (slow, opt-in)
make build       # Compile the plugin
make package     # Build a candidate tarball and artifact manifest

make check does not run mutation testing by default. Set MUTATION=1 for a one-off run, or export FORGELOOP_MUTATION=1 on a machine that should include it in every full check; make check-fast and make precommit never run mutation. CI keeps mutation in the nightly shard matrix rather than the quick quality job.

For installation, model configuration, and profile selection, follow the deployment guide and plugin guide. make verify-plugin runs a real host/model smoke test, and make verify-e2e runs the full real-model, real-tool delivery path from a candidate tarball; both require model authentication and are described in the deployment guide.

Documentation

Most detailed project documentation is currently in Chinese.

Document Contents
Product and first-release plan Goals, scope, design decisions, and validation rules
Status and evidence Implemented capabilities, checks, installation records, and known gaps
Architecture Current modules, persistence, and external interfaces
Domain language Business objects, identities, and lifecycle terminology
Plugin guide Plugin entry points and configuration
Deployment guide Installation, upgrades, validation, and recovery
Documentation index Design decisions and historical records

Contributing and license

Read AGENTS.md and CONTRIBUTING.md before making changes. Keep changes scoped, preserve ongoing work, and support critical behavior with tests and actual execution evidence.

A license for the code and documentation has not yet been selected. See CONTRIBUTING.md for the current distribution policy.

—/ 5

No ratings yet

Manifest verification required

Commit c287085724c5

Community comments

No comments yet. Be the first to write one.

DSH HUB

A community index for DSH plugins. Not an official GitHub or DeepSeek AI product.

CommunityResourcesAPIAbout