Tencent's LoopForge Installs With Docker Socket Access and Listens on All Interfaces
Software / news
Tencent's LoopForge Installs With Docker Socket Access and Listens on All Interfaces
The MIT-licensed coding-agent workspace has 1.6k stars, ten supported agent CLIs, and a security section its quick-start does not lead with.

Tencent's LoopForge, a self-hosted workspace that hands software tasks to coding agents, installs with access to the host's Docker socket and, on new installs, listens on every network interface. Both defaults are written in the project's README on GitHub.
The repository, MIT licensed, shows 1.6k stars, 281 forks, 45 issues and 41 pull requests. The README describes it as "a self-hosted workspace where your team ships software with coding agents." No individual author is named on the page, and the Releases section is empty.
How the workflow runs
A user describes work to a chat bot. LoopForge opens a Docker sandbox holding the repositories, delegates to project roles and opens a pull request. Repeatable workflows are saved as SOPs, standard operating procedures built from Agent, Script, Human-gate, Sub-SOP and Preview build nodes.
Each node declares its artifacts and dependencies, and "the engine starts each step once its dependencies complete." A human gate can approve a step or send it back to an earlier one.
The README lists ten supported coding-agent CLIs: CodeBuddy, Codex, Claude Code, OpenCode, Cursor CLI, Antigravity, Kimi Code, Pi, DeepSeek Harness and ZCode. It ships four built-in SOPs: backend, frontend, bug-fix and product.
What the security section says
Three statements matter to anyone about to run ./start.sh.
| Default | README wording | Fix named in README |
|---|---|---|
| Docker access | "Docker socket access grants control of the host daemon" | Use for trusted teams only |
| Network exposure | "New installations listen on all interfaces" | Set up HTTPS first |
| Project data | "signed-in users can read project data across the instance" | Set AGENTFLOW_ALLOW_SIGNUP=false |
The README says the Docker setup suits trusted teams, not untrusted multi-tenant use. Docker's own security documentation says "only trusted users should be allowed to control your Docker daemon," and that the daemon "requires root privileges unless you opt-in to" rootless mode.
Put together, a LoopForge instance reachable over a network, with sign-up open, lets any account holder read every project and sits one hop from root on the host. Teammates can sign up from the login page unless the variable above is set to false in .env.
What the evidence for it amounts to
The project's own validation claim is narrow. The README says: "Three real tests passed; the run waited for human approval, then verified the accepted code had not changed." It points to a validation record for scope and known gaps, which The Terminal did not fetch.
The README also says token and cost accounting runs "at public list prices." These are the project's own figures. No independent party is named as having run the workflows.
Installation needs Git, Docker, Compose, Python 3 and curl, and ./start.sh pulls a release image pinned in compose.yaml. A local mode skips the platform and needs Node.js 20 or newer, Python 3.8 or newer and an installed coding assistant. Development from source needs Go 1.26.11 or newer.
Other agent tooling is arriving with the same trust questions. Alibaba's OpenCodeReview makes vendor claims about token cost, and the copyright question over agent-written output is covered in the Copyright Office piece.
The first thing to check on a LoopForge install is the bind address in .env. The README says existing settings are kept on upgrade, so an instance started before the default changed keeps whatever it had.
Sources
More in Software
- 01Zigzag, a 35 MB Mac Browser, Courts Arc Users 35 Days Before ShutdownThe WebKit-based browser imports Arc spaces and pinned tabs, but its README lists no sync, no Boosts and a partial Chrome extension API.
- 02Nimony 0.6.2 Sets a Year-End Goal for Nim 3 With 44 Days LeftThe compiler that will become Nim 3 is MIT-licensed and builds natively without LLVM, but its FAQ says it cannot yet compile Nim 2 code unchanged.
- 03Alloy CSS Runs Menus and Tabs Without JavaScript, but Dialogs Need Safari 26.2The 24 KB MIT stylesheet leans on popover and invoker commands, so its no-script promise has browser floors that differ by component.
- 04Windows 11 Telemetry Flags Which Coding Agents You Run, Researcher FindsXusheng Li traced a service-experiment feature in build 26200.9974 that matches executable names such as claude.exe and queues the result as optional diagnostic data.