Repository navigation
Add the self-hosted LoopForge platform; move the CLI into cli/ - #46
Open
Robert0622 wants to merge 43 commits into
Open
Robert0622 wants to merge 43 commits into
Robert0622 wants to merge 43 commits into
Conversation
The repository root is about to host the self-hosted LoopForge platform, so the CLI moves to its own directory with paths, packaging metadata and CI working directories adjusted to keep it building and releasing unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
Teams need the same SOP-driven delivery that the CLI gives a single agent, but shared, auditable and running on their own machines, so the platform (server, web studio, runners, REST and MCP APIs) becomes the primary project here under Apache-2.0 while the CLI keeps its MIT license. Co-authored-by: Cursor <cursoragent@cursor.com>
The mirror only worked with an SDK that is not publicly available, so it was dead code for every open-source user; local metrics and the dashboard keep working unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
…oadmap The README now leads with the three things that set LoopForge apart (the automated requirement loop, observable and evaluable runs, expert SOPs with shared context), explains run isolation and the MySQL migration step, and points to a roadmap; operator docs and migration comments lose their internal-history tone. Co-authored-by: Cursor <cursoragent@cursor.com>
Platform tags now also create a "LoopForge Platform" release marked latest, CLI releases are titled "LoopForge CLI" without claiming latest, and platform jobs get prefixed check names so the two release lines and their status checks stay distinguishable. Co-authored-by: Cursor <cursoragent@cursor.com>
Per-run environment isolation is a core promise, but inside the container the platform fell back to local processes. The image now ships the Docker CLI, compose mounts the host socket, and bind sources are translated through the platform container's own mounts so each run gets a fresh container on the host's Docker, joined to the compose network. Co-authored-by: Cursor <cursoragent@cursor.com>
Git 2.5x rejects `git add -u` pathspecs when the index is empty, which failed delivery for freshly initialised repositories on current CI runners; there is nothing to update in that case. Co-authored-by: Cursor <cursoragent@cursor.com>
Merging the two trees left AGENTS.md as a self-referencing include, so agents and contributors got no layout rules; the internal history notes are replaced with how to run and verify the platform. Co-authored-by: Cursor <cursoragent@cursor.com>
The demo SOP simulates every step, but dispatch still attached the project's default repository, so trying the demo after binding a repo failed on a clone it never needed. Co-authored-by: Cursor <cursoragent@cursor.com>
…r in view New users finished the tour without knowing what to do next, and the credential save button sat at the bottom of a long form. The dashboard now shows a live checklist with direct actions and a one-click demo run, the tour starts there, and the save bar sticks to the viewport and flags unsaved edits. Co-authored-by: Cursor <cursoragent@cursor.com>
The built-in mock executor writes its own gate result, yet provisioning still required the gate MCP binary, so demo runs failed on standalone binaries. Missing helpers are now reported at startup with how to fix the install, and a binary inside a checkout's bin/ finds its source from any working directory. Co-authored-by: Cursor <cursoragent@cursor.com>
Apache 2.0 for the platform and MIT for the CLI was a compliance risk; use MIT everywhere and keep third-party notices unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
`make run` / `make demo` now build the gate MCP helpers and point at them, and `./start.sh` pulls GHCR or builds from the checkout with demo mode on so a fresh clone works without inventing a deploy script. Co-authored-by: Cursor <cursoragent@cursor.com>
Users get lost after the tour; a home chatbot lets them clarify in one sentence, dispatch, and watch running or waiting workflows in the same view, with a one-click demo when no API key is set. Co-authored-by: Cursor <cursoragent@cursor.com>
Fixed demo login, a short quick-fix SOP, credential wizard, humanized errors, WeCom notify hooks, and login-free approval share links so users can start without scraping compose logs or babysitting the UI. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep the same group-chat webhook behavior; only rename the public docs and comments so platform hygiene stays green. Co-authored-by: Cursor <cursoragent@cursor.com>
./start.sh -y installs missing curl/git/Docker/Compose when possible, pulls GHCR (or builds), waits on /api/health, and prints admin/demo1234. install.sh enables a curl|bash bootstrap without a prior clone. Co-authored-by: Cursor <cursoragent@cursor.com>
…rter start.sh - /api/doctor reports sandbox isolation, sandbox image, gate helper, model key, Git token, CLIs and notifications; the guide shows it with fix buttons and admins can prewarm the sandbox image from there - loopforge --self-test (./start.sh doctor) logs in, runs one demo requirement, approves it through the public share link and checks the delivery report - the default sandbox image builds in the background on first start - start.sh keeps command-line variables over .env, moves to a free port, builds the cloned checkout (release tags pull), falls back to Go/npm mirrors, checks disk space, and adds warm/reset; compose gains a healthcheck and passes the notify/public URL settings Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
- built-in agent nodes fall back to the CLI the user has a key for, so the default quick-fix SOP runs with only a CodeBuddy (or Codex) key - saving a CodeBuddy key verifies it against the international and China sites and stores the network environment that works - home chat shows clarification errors instead of an empty "done"; a 401 from the model returns a credential hint at once instead of three retries - the login form shows the demo account while demo mode applies Co-authored-by: Cursor <cursoragent@cursor.com>
- home chat reads the clarification from the done event, shows answer options, and run cards show the requirement title and open its issue - approvals page loads full run snapshots, so it names the waiting node and explains planned approval nodes instead of reporting a failed gate - external approval links show the requirement and the upstream result - demo executor writes a readable sample result instead of echoing the prompt - loopback OTLP export works when login is required Co-authored-by: Cursor <cursoragent@cursor.com>
The quick-fix and demo agents have no task prompt, so their prompt carried only the issue identity block and agents could not see what to build. The run input (and, without a brief, upstream results) is now always included. Dispatch input no longer repeats a title that the description starts with. Co-authored-by: Cursor <cursoragent@cursor.com>
- dispatch refuses a run whose bound GitHub repository cannot be pushed because the responsible user has no git token (and no execution machine) - home chat tells apart a created issue that could not start, and its settings / open-issue buttons now work - executor fallback is recorded in the run telemetry - unbound-repository clarification shows a neutral hint instead of a repository fetch failure; run cards translate waiting / paused - README names the 直接创建 button Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
- importing an issue from a public repository reads it anonymously; a failure explains that private repositories need a GitHub token - import errors stay on screen as error toasts - the git-token refusal and doctor hint point to 个人设置 and say when the token is needed Co-authored-by: Cursor <cursoragent@cursor.com>
…tool calls in run evaluation facts Co-authored-by: Cursor <cursoragent@cursor.com>
…xecutor that will actually run Co-authored-by: Cursor <cursoragent@cursor.com>
…quick-fix once a model key is set; localize sync logs Co-authored-by: Cursor <cursoragent@cursor.com>
…oken is set Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…op rerun on approval gates Co-authored-by: Cursor <cursoragent@cursor.com>
…o SOP once a key is set Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…efault to docker Co-authored-by: Cursor <cursoragent@cursor.com>
Robert0622
force-pushed
the
platform-integration
branch
from
October 13, 2026 03:54
6ba7a4e to
f5f0b06
Compare
In docker compose the hostname is the container ID, which changes on every recreate. Runs bound before an upgrade then looked foreign: their idle sandbox containers were never reclaimed, and a retry rebuilt the workspace from the remote branch, dropping unpushed changes. Co-authored-by: Cursor <cursoragent@cursor.com>
…at pages - No built-in password: without LOOPFORGE_ADMIN_PASSWORD the first visitor creates the admin in the browser and adopts the ownerless default project. - Self-registration from the login page, open by default; admins toggle it under 平台管理 (LOOPFORGE_SIGNUP=closed sets the default). - 个人设置 is split into 模型 Key / 代码仓库 / MCP 令牌 / 账号 tabs routed as #/settings/<tab>; switching tabs keeps unsaved input. - 发起需求 gets its own page; 工作总览 keeps the checklist and status only. - The tour starts at 发起需求 and ends on the settings tab that still needs a key; the credential wizard no longer pops up by itself. - Self-test signs an admin session inside the deployment instead of using a demo password. - Playwright: first-run setup (second server without an admin), registration and the sign-up switch, settings tabs, account tab, chat/dashboard split. Co-authored-by: Cursor <cursoragent@cursor.com>
…the tab closes - 发起需求: clear the busy state before the final render so the composer unlocks after 建单并开跑, and retire the stale inline dispatch button. - CodeBuddy key verification no longer stops when the browser disconnects, so the detected network environment is still saved. Co-authored-by: Cursor <cursoragent@cursor.com>
…tons Hovering a toast pauses its dismissal, so one sitting on a drawer's close button blocked closing the drawer for as long as the pointer stayed there. Co-authored-by: Cursor <cursoragent@cursor.com>
… panel The page now opens on a centered composer with SOP cards. Clarify questions come back as clickable options with a completeness meter, and a launch card appears once the requirement is clear. Sending a message without a model key explains what is missing instead of starting the demo. Run progress for every active SOP, step by step, lives in a collapsible panel on the right. Co-authored-by: Cursor <cursoragent@cursor.com>
The home chat now talks to the platform assistant in a PM role instead of only clarifying new requirements. It can read attached images and files, @-reference existing requirements, check run progress, propose writes as drafts confirmed through /mcp, return generated files and mermaid diagrams, and still clarify with option questions before offering a launch card. The dashboard view is gone: the brand and the first nav entry open 首页, old #/dashboard links land there, the quick-start checklist moved to the guide page, and the issue drawer gets a button to discuss a requirement on the home page. Mermaid is vendored so diagrams render under the CSP. Co-authored-by: Cursor <cursoragent@cursor.com>
…unctuation, name draft targets Co-authored-by: Cursor <cursoragent@cursor.com>
…launch it twice Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
LoopForge now ships two parts in one repository:
cli/): the existing workflow installed into a single coding agent. Unchanged for users:npx -y loopforge-cli@latest install <agent>and the npm release workflow keep working. MIT.Commits:
cli/(pure moves plus path and CI fixes).platform-v*) and CLI (v*) releases distinct names.docker composedeployment.Verified locally:
go vet,go test ./..., API e2e, Playwright (31 tests), CLIvalidate.sh, internal-reference and gitleaks scans, a compose deployment running concurrent runs in separate sandbox containers.Made with Cursor