Bundle coding agent teams into a single workflow for repeatable software delivery
When you assign bug fixes to coding agents, the results vary each time, making it hard for teams to trust the output. LoopForge is a workspace that bundles agents, scripts, and human approval steps into a single flow to deliver software repeatedly in the same way. It runs on your own server, allowing you to transparently track the process and results of the agents' work.
Interactive exploration and fixed workflows
LoopForge provides two paths: interactive exploration and fixed workflow execution. The interactive mode is suitable for immediate fixes or idea validation by chatting with the Main Bot, where the agent opens a Docker sandbox, checks out the repository, divides roles, and generates a PR. The SOP (Standard Operating Procedure) mode is a structure where agents, scripts, and human approval gates execute in a defined order, used for repetitive delivery tasks. Both modes track the same requirements, linking all changes to their originating request and reflecting them in cost reporting.
Role separation and human control
Each stage of planning, implementation, review, and testing is defined as an independent role with its own prompt, executor, model, and rules. This prevents agents from reviewing their own code or skipping tests. Human approval gates are placed at critical points, allowing you to review reports and approve or roll back tasks to specific stages. You can view node status, tool traces, logs, and artifacts in one place during execution, and retry failed steps or resume after interruption.
Installation and execution environment
Installation requires Git, Docker, Python 3, and curl, with the installation script automatically installing any missing components. The ./start.sh command fetches the GHCR release image, creates MySQL and platform services, and installs the default sandbox, starter SOP, and welcome project. You do not need Go or Node.js installed on the host. The service listens on all interfaces on port 0.0.0.0:8090 by default; on cloud hosts, you must allow this port in the security group or place an HTTPS reverse proxy in front. Docker socket access permissions allow control of the host daemon, making it suitable for internal use by trusted teams.
Suitable targets and verification items
LoopForge is suitable for teams using coding agents to deliver software, particularly when you want consistency and approval procedures in repetitive delivery processes. If a single developer wants to use built-in workflows in an IDE or CLI, they can choose LoopForge Local. Before use, you must verify the security impact of Docker socket access permissions, the account and access model, and the API key requirements for each executor. It is provided under the MIT license, and third-party components follow their respective licenses.