LoopForge Local workflow
LoopForge Local adds a role-based dev workflow to Claude Code, Codex and Cursor: analysis, design, code, review and tests.
- 613 ★ on the repository
- Last commit
Extended access
Why this level
- Following the workflow the assistant edits code and runs tests in your project, and the installer adds files to the repository.
Install
- Works in
Manual install
npx -y loopforge-cli@latest install claudeThe command from the LoopForge Local section of the README. Start the workflow with `/start-devflow "<request>"`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Following the workflow the assistant edits code and runs tests in your project, and the installer adds files to the repository.
This is third-party code. Review the repository files before installing.
What it does
LoopForge Local is the part of Tencent's LoopForge project that runs a development workflow right inside the coding assistant you already have, with no server or Docker. The command `npx -y loopforge-cli@latest install claude` places roles and commands in the project, and `/start-devflow "<request>"` starts the chain. The agent first studies the project and clarifies the goal, scope and acceptance criteria. Medium and large tasks move on to design and code only after you confirm. Design, development, review and testing are handled by roles with separate responsibilities, which reduces self-review bias in a single context. Small edits get a short single-role path. Requirements, plan, changes, review findings and test results are saved to `artifacts/{task_slug}/`. Workflow state is stored on disk, so the next session resumes at the unfinished stage. CodeBuddy, Codex, Cursor and Claude Code are supported, and the lighter edition also covers Pi, DeepSeek Harness and Hermes Agent.
Who it is for. Developers and tech leads who want an agent to run a task by stages with review and a decision trail, without setting up a separate platform.
Good fit when
- A large task must pass through stages: requirements, design, code, review, tests.
- A session was interrupted and work must resume from the unfinished stage with `/resume-devflow`.
- State and results must be checked with `/status-devflow` and in the `artifacts/` folder.
- Codex or Cursor needs the same process as Claude Code.
Not a fit when
- You need a team platform with Docker sandboxes, shared SOPs and approvals: that is the platform part of the project.
- A one-line edit: a short path exists but the full process is excessive.
- Node.js 20 and Python 3.8 are missing.
Example request
Start the development workflow for this task: add status filtering to the order list and cover the API with tests. Wait for my confirmation before implementing.Limitations
You need Node.js 20 or newer, Python 3.8 and a coding assistant. The installer allows only one edition per assistant in a project, Classic by default or Portable; `install --force` switches. Platform SOPs cannot yet be exported for standalone local runs. Before installing, `loopforge plan claude` shows what will change in the project, and state is recorded in `.devflow/install-state.json`. Hermes Agent asks you to trust the repository with `hermes skills trust .`. The last commit dates from November 2026.
How to disable. Check the installation with `npx -y loopforge-cli@latest status claude`. To remove it, use the files in `.devflow/install-state.json` as the list of managed files and delete them by hand.
FAQ
How do I install LoopForge Local in Claude Code?
In the project root run `npx -y loopforge-cli@latest install claude`. Check the installation with `npx -y loopforge-cli@latest status claude`.
Which commands start the workflow in other agents?
Codex uses `$devflow-codex "<request>"`, CodeBuddy and Cursor use `/start-devflow "<request>"`, and DeepSeek Harness and Hermes Agent use `/devflow "<request>"`.
How do Classic and Portable differ?
Classic is the default and gives `/start-devflow` commands with role agents. Portable relies on the `skills/` folder and shared `/devflow` skills, and also suits Pi, DeepSeek Harness and Hermes.
What if installation or a run fails?
Run `npx -y loopforge-cli@latest doctor`: the command diagnoses the environment.
Is an API key needed?
LoopForge Local needs no key of its own: requests go through the installed assistant, so you need that assistant's own credentials.
Discussion
No questions or reviews yet.
Related
WorkflowsA CLI and Claude Code plugin taking GitHub issues through checks, plan, code, review and CI to merge, in parallel lanes
A skill for Codex and Claude Code that turns ideas and bugs into working code through a writer, tester and reviewers
A plugin with ready, go and migration commands: it settles what you want first, then builds and verifies the result
A Claude Code plugin: Claude does the task, then a stop hook starts an independent Codex review and Claude fixes the findings in the same session
A workflow template for Claude Code and five more agents: a backlog task, a diff review and a commit.
Factory Factory runs Claude Code and Codex in parallel, each in its own git worktree, with diffs and terminal in one window.
README in short
The local part of the project carries the built-in Classic and Portable workflows and does not yet import platform SOPs. The rest of LoopForge is a standalone server for teams.