Reading the repo
Opening the box…
Reading the repo
Opening the box…
How to install on Linux
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
Saved setup from 8 h ago
Will it work on Linux?
Heads-upIt also needs MySQL and 12 settings in .env (3 secret).
The maintainers included start.sh. Run it from the cloned folder after reading it.
bash start.sh
Also: scripts/install.sh, scripts/install-observability-schema.sh, scripts/install-playwright-deps.sh, scripts/install-schema-extensions.sh
Then run bash setup.sh. It stops at the first error and is safe to run again. Servers and tests aren't started; it lists them at the end. Read it first.
git clone https://github.com/Tencent/LoopForge.git cd LoopForge
Go 1.26.11
sudo snap install go --classic # or https://go.dev/dl/
Fill in secrets: AGENTFLOW_SESSION_SECRET, LOOPFORGE_DB_PASSWORD, LOOPFORGE_DB_ROOT_PASSWORD
cp .env.example .env
Needs: MySQL
# needs Docker Engine: https://docs.docker.com/engine/install/ docker compose -f compose.yaml up -d
go mod download
go test ./...
Install Git and clone the repository first. The installer checks Docker, Compose, Python 3 and curl and offers to install missing components. Python/curl installation supports apt, dnf and yum on Linux; the Compose plugin supports x86_64/arm64 and verifies the official release SHA-256. macOS needs a working Python 3 and Docker Desktop; Homebrew can install missing components. Ordinary Linux users are supported through Docker group access or sudo. Set LOOPFORGE_YES=1 to accept installation prompts. Package and image downloads require internet access.
git clone https://github.com/Tencent/LoopForge.git
cd LoopForge
./start.sh
./start.sh pulls the GHCR release image pinned in compose.yaml without building locally (bash scripts/install.sh does the same). It creates the MySQL and platform services, generates configuration and session secrets, and installs the built-in sandboxes, starter SOPs and welcome project. Host Go and Node.js installations are not required. Configure model API keys and GitHub authorization after startup. Use ./start.sh logs, stop, restart or pull to manage it, and ./start.sh dev to build the checkout from source.
If downloads from ghcr.io stall, set MIRROR to a registry host that can stand in for ghcr.io. ./start.sh pulls from that host and tags the image back to the name pinned in compose.yaml. Setting MIRROR trusts that host, because the download is tagged with the official name. The GitHub Release records the digest; docker image inspect --format '{{index .RepoDigests 0}}' ghcr.io/tencent/loopforge:<pin> should show the same digest after @. Without MIRROR, ./start.sh still pulls ghcr.io directly, and compose.yaml stays unchanged. Upgrade with the same variable and ./start.sh pull. ghcr.nju.edu.cn is one such host. A Docker registry-mirrors entry such as https://docker.nju.edu.cn only accelerates Docker Hub and is not a value for MIRROR.
MIRROR=ghcr.nju.edu.cn ./start.sh
Open the address printed by the installer and create your account; the first one becomes the administrator. The service listens on 0.0.0.0:8090 by default. On a cloud host, the installer reads the public IP from the provider's metadata service and prints it; allow the port in your security group, or put an HTTPS reverse proxy in front. Restrict access to your own IP until the administrator account exists. The home page's quick-access guide walks you through adding a model key, connecting a repository and choosing an SOP.
For GitLab, Gitea, Gogs and other Git hosts, set up Git SSH to check out and push branches with a personal key. PR/MR and Issue automation requires a hosting API token or a separately configured MCP.
New accounts join the LoopForge demo project, which includes an SOP made only of a script and a human gate:
| I want to… | You need | | --- | --- | | Run the script + approval demo | Nothing | | Chat with Main Bot, generate a document or a new project | An API key for the selected executor | | Change an existing repository (in chat or via an SOP) and open a PR | Model credentials and a GitHub repository (connect GitHub in personal settings) |
<details> <summary><b>More setup details</b>: executors, GitHub, sandboxes, access model</summary> <br>Executors. Pick one of ten CLIs beside the home composer, then a model. Every SOP role can choose its executor independently (built-in roles default to CodeBuddy). Requirement clarification, AI notification summaries, Bot replies and run evals currently use CodeBuddy, so their model pickers list CodeBuddy models only and the server refuses a model of another CLI instead of switching it to CodeBuddy; scheduled assistant tasks run on the CLI the task selects.
| Executor | Credentials | Installation | | --- | --- | --- | | CodeBuddy | Personal key, or a shared key an administrator configures for chat and SOP runs | In the Docker image | | Codex | Personal key; a connected execution machine can use its local login | In the Docker image | | Claude Code | Personal key; a connected execution machine can use its local login | Installed from npm on first use, then cached | | OpenCode · Kimi Code · Pi | Personal key only | Installed from npm on first use, then cached | | DeepSeek Harness | Personal key only | In the Docker image | | Cursor CLI | Personal key only | Provider installer on first chat use; not installed into SOP sandboxes | | Antigravity | Personal key, or the con
…
No reports for Linux yet.
GitManual AI Agent reads the 13 key files and writes a step-by-step guide for Linux. Once written, it's saved for everyone.