Skip to content

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.

3.2 KB
Raw Blame

LoopForge Local

旧版(Legacy)。 已发布的 loopforge-cli 版本仍可安装。平台项目和 SOP 可通过 LoopForge MCP 接入。

Legacy. Previously published versions of loopforge-cli remain available. To work with platform projects and SOPs, connect to LoopForge over MCP.

LoopForge 的本地工作流组件,在 CodeBuddy、Codex、Cursor、Claude Code、Pi、DeepSeek Harness 或 Hermes Agent 中使用,无需启动平台。

Local workflows for LoopForge, running inside an existing coding assistant without the platform server.

Requires Node.js 20+ and Python 3.8+, plus a supported coding assistant. This npm package installs Local workflows, not the Docker platform.

需要 Node.js 20+、Python 3.8+ 和受支持的编程助手。此 npm 包安装本地工作流,不安装 Docker 平台。

Classic workflows configure agent execution permissions and hooks. Review the generated configuration before use; only install into projects you trust and back up existing settings. See the security policy.

Classic 工作流会配置 Agent 执行权限与 Hook。使用前请检查安装配置,仅安装到可信项目,并备份已有设置;权限边界见安全政策。

# Run in the project where you want to install the workflow.
# 在需要使用工作流的目标项目中运行。
# Replace X.Y.Z with the published version for your setup.
# 将 X.Y.Z 替换为与你的环境匹配的已发布版本。
npx -y [email protected] install claude
npx -y [email protected] status claude

Start with /start-devflow "<request>" in Claude Code. Replace claude with codebuddy, codex, or cursor when installing for another host; use skills install pi, skills install dsh, or skills install hermes for Portable hosts. DSH uses /devflow "<request>" after installing the Skill, and the optional DSH plugin adds /loopforge task controls. Hermes loads the project skill after hermes skills trust .; its optional native plugin adds the same /loopforge controls.

在 Claude Code 中通过 /start-devflow "<需求>" 启动。其他宿主的安装命令、入口及 Portable 用法见统一文档。

已有包名 loopforge-cli、devflow-workflow 和 loopforge 命令保持兼容。

Existing package names and commands remain compatible.

Third-party notices are maintained at the repository root. Packaging generates a local notice and includes it with LICENSE in npm, Python and release archives. Project policies and release history are shared at the repository root.