Chorus Agent工作流
Chorus Agent工作流 是 AI Skill Hub 本期精选Agent工作流之一。综合评分 8.2 分，整体质量较高。我们强烈推荐将其纳入你的 AI 工具库，帮助提升工作效率。
📚 深度解析
Chorus Agent工作流 工作流的设计遵循"最小配置，最大复用"原则：核心逻辑已经封装好，用户只需配置自己的 API Key 和业务参数即可快速上手。工作流内置错误处理和重试机制，在网络波动或 API 限速等情况下仍能稳定运行，适合作为生产环境的自动化基础设施。
在实际部署时，建议先在测试环境中运行 3-5 次，验证各个环节的输出结果符合预期，再部署到生产环境。AI Skill Hub 评分 8.2 分，是同类 Agent 工作流中的精选推荐。
📋 工具概览
Chorus Agent工作流 是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。
📖 中文文档
Chorus Agent工作流 是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。
- 可视化 Agent 工作流编排，无需编写复杂代码
- 支持多步骤自动化任务链，实现全流程无人值守
- 与外部 API、数据库和第三方服务无缝集成
- 内置错误处理与自动重试机制，保障稳定运行
- 提供可复用的自动化模板，快速在同类场景部署
- 自动化日常重复性工作，将精力集中于创造性任务
- 构建数据采集 → 处理 → 输出的完整自动化管线
- 实现跨平台、跨系统的数据流转和业务协同
# 方式一：npm 全局安装 npm install -g chorus # 方式二：npx 直接运行（无需安装） npx chorus --help # 方式三：项目依赖安装 npm install chorus # 方式四：从源码运行 git clone https://github.com/Chorus-AIDLC/Chorus cd Chorus npm install npm start
- 访问 GitHub 仓库获取工作流文件
- 在对应平台（Dify / Flowise / Make 等）中找到「导入工作流」功能
- 上传工作流文件
- 按照提示配置必要的环境变量和 API Key
- 运行测试确认流程正常后投入使用
# 命令行使用
chorus --help
# 基本用法
chorus [options] <input>
# Node.js 代码中使用
const chorus = require('chorus');
const result = await chorus.run(options);
console.log(result);
# chorus 配置说明 # 查看配置选项 chorus --config-example > config.yml # 常见配置项 # output_dir: ./output # log_level: info # workers: 4 # 环境变量（覆盖配置文件） export CHORUS_CONFIG="/path/to/config.yml"
简介
<p align="center"> <img src="packages/landing/public/images/chorus-slug.png" alt="Chorus" width="240" /> </p>
<p align="center"><strong>The harness for your coding agents. Agents propose, humans verify, software ships.</strong></p>
<p align="center"> <a href="https://discord.gg/SwcCMaMmR"> <img src="https://img.shields.io/badge/Discord-Join%20us-5865F2?style=for-the-badge&logo=discord&logoColor=white" alt="Discord"> </a> <a href="https://github.com/Chorus-AIDLC/Chorus/actions/workflows/test.yml"> <img src="https://img.shields.io/endpoint?url=https://gist.githubusercontent.com/ChenNima/f245ebf1cf02d5f6e3df389f836a072a/raw/coverage-badge.json" alt="Coverage"> </a> </p>
<p align="center"><strong>English</strong> · <a href="README.zh.md">中文</a> · <a href="README.ko.md">한국어</a> · <a href="README.ja.md">日本語</a></p>
<p align="center"><a href="https://doc.chorus-ai.dev"><strong>📖 Documentation</strong></a></p>
Chorus is the harness for your coding agents. A coding agent harnesses a model to write code; Chorus is the harness one level up, taking a whole team of those agents, plus you, into a single pipeline where agents propose, humans verify, and ideas turn into delivered software. Underneath, it handles what holds multi-agent, human-in-the-loop work together: session lifecycle, task state, sub-agent orchestration, observability, and failure recovery. Every AI Agent gets fine-grained, configurable permissions.
Inspired by the AI-DLC (AI-Driven Development Lifecycle) methodology. Core philosophy: Reversed Conversation — AI proposes, humans verify.
---
What's New
v0.23.0: Manage workspace-local accounts and personalize display names and avatars. Adds proposal dependency validation, optional Pi pre-submit checks, and shared Redis auth rate limits; fixes task actor attribution and duplicate mention notifications.
v0.22.2: Host Chorus on your own Linux or macOS machine with Docker Compose and PostgreSQL 17, with repeatable deployment, optional LAN HTTPS, and Cloudflare Tunnel guidance. TRAE CLI joins the existing workflow through the shared Codex plugin. This release also fixes stale assignments, deletion failures, and daemon security and configuration issues.
v0.22.0: Hermes Agent now joins the existing Chorus workflow through its own gateway, with no separate Chorus daemon. Assign work in Chorus, run it in Hermes, and bring results and approval requests back to the project. Install through the Chorus CLI or directly with Hermes.
v0.21.0: Private projects and project groups provide Viewer, Editor, and Admin access with live permission inheritance. Agent startup and execution failures now include persistent diagnostics in conversations. This release also improves Linux daemon persistence and updates security dependencies.
v0.20.0 — Daemon backends now use Codex App Server, bidirectional Claude Code stream-json, and native Pi RPC for protocol-based interruption and execution tracking. New chorus upgrade updates npm-global CLI installations; --plugins also refreshes configured Claude Code, Codex, Kiro, and Pi integrations.
v0.19.1 — Lightweight Research checks factual gaps during Idea and Proposal preparation. Inline evidence citations put sources next to claims, and Tracker can request more research before development starts.
v0.19.0 — Cloudflare-inspired reviewer rules: clearer scope, complete blocker evidence, and stable finding IDs across rounds. Task reviews now check code quality beyond acceptance criteria.
v0.18.0 — Built-in spec-lite adds a lightweight, Git-native local spec workflow alongside OpenSpec. Live session anchors let daemon agents return replies to the initiating agent's existing Idea session.
v0.17.2 — Pi is now a published, wakeable Chorus agent, and chorus agents run switches local agent profiles with one command.
v0.17.0–0.17.1 — One CLI now installs and refreshes Chorus across your coding agents. Live daemon activity is visible directly on Ideas in Tracker, Graph, and detail views.
Full changelog: CHANGELOG.md
---
Quick Start
Two commands. No database, no Docker, no config files.
npm install -g @chorus-aidlc/chorus@0.21.0
chorusChorus starts with an embedded PostgreSQL (PGlite), runs migrations, and opens at http://localhost:8637. Default login: admin@chorus.local / chorus.
Running multiple agents or deploying to production? Use an external PostgreSQL, Docker, or AWS → Deploy & self-host.
Hosting on your own machine or connecting a Cloudflare Tunnel? See Self-host on a local machine for installation, LAN HTTPS, and Cloudflare Named Tunnel setup.
To turn your local machine into an agent runtime that picks up assigned tasks, run chorus daemon → Daemon operations · Remote control.
Upgrade the CLI and plugins
chorus upgrade # CLI only; `chorus update` is an alias
chorus upgrade --plugins # Also refresh configured agents' Chorus pluginsSelf-upgrade supports the active npm global installation on Linux, macOS and Windows. It checks npm's prefix, resolves the latest stable release, avoids downgrades and verifies the installed version. Source checkouts, links, npx and other package-manager installations must use their own update workflow. CLI discovery, installation or verification failure stops plugin work.
--plugins reads ~/.chorus/daemon.json, including legacy single-agent records. Explicit Claude Code, Codex, TRAE CLI, Kiro and Pi types are processed even with wake disabled. Each record's home, config directory and PATH are respected; shared destinations update once. Only Chorus and required integration packages are refreshed, with existing credentials and unrelated settings preserved. Host CLIs must already be installed. Kiro templates come from the record's configured Chorus instance (its served version, which may lag npm); conflicting instance URLs for one destination are reported. Stable Pi >=0.99.0 <2.0.0 uses native MCP and targets Chorus only; Pi 0.84.4–0.98.x retains the verified pi-mcp-adapter@5.0.0 pin. Unknown versions do not trigger adapter changes or an MCP-complete claim; unsupported hosts run no package commands. Updates are targeted, never all-extension; missing capability or incompatible constraints report incomplete work. User pins/ranges are preserved (the verified adapter pin is intentional, not an incomplete latest refresh). Existing native-host adapters and -builtin:mcp filters produce scope-specific manual-migration warnings, never automatic removal. See Pi setup.
The command is noninteractive and reports each target. Exit 0 means all requested work completed (missing/empty configuration is a successful no-op); exit 1 means failure or incomplete work, including offline/unknown/untyped records, missing hosts or unsupported targeted updates. Later targets still run after a plugin failure; completed changes are not rolled back. Start new agent sessions and restart the daemon when convenient to activate updates—the command does not restart processes or interrupt sessions.
npm installation has no automatic deadline or forced kill; it shows sanitized progress until npm exits. Queries remain time-limited. Failures include sanitized causes and exit status; permission failures suggest a user-owned Node installation such as nvm. Existing config backups use one .chorus-upgrade.bak per file, replaced on the next upgrade.
---
AI-DLC Workflow
Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Verify ──> Done
^ ^ ^ ^ ^ ^
Human idea:write proposal:write task:write *:admin *:admin
creates + elaborate + drafts + reports + verifies + closesThe labels under each stage are the permissions an actor needs there — granted to a human, an Agent, or both. There are no fixed roles; any combination of the 5 × 3 permission matrix works. → Agent permissions
---
Chorus 是一个 AI 人机协作的代理工具，旨在促进人机之间的高效协作。
Chorus 的功能包括会话生命周期管理、任务依赖关系图、Kanban 流程管理、多代理协作、细粒度代理权限管理等。
Chorus 需要一个稳定的网络环境，支持多种数据库和消息队列系统，包括 PostgreSQL、Redis 等。
Chorus 支持多种部署方式，包括 npm、Docker、AWS CDK 等，用户可以根据自己的需求选择合适的部署方式。
Chorus 的使用教程包括快速启动、配置管理、任务管理等方面，用户可以通过这些教程快速上手 Chorus。
Chorus 的配置管理包括 MCP、环境变量、关键参数等方面，用户可以通过这些配置项来定制 Chorus 的行为。
Chorus 的工作流包括idea、proposal、document、task、execute、verify、done等阶段，用户可以通过这些阶段来管理项目的整个生命周期。
Chorus是AI工作流领域的优秀开源项目，融合Agent框架和人机协作理念，841星的热度反映社区认可度。TypeScript实现便于集成，适合现代AI应用开发。
- 需要让 Claude / Cursor 操作本地工具的 AI 工程师
- 构建多智能体协作系统的 Agent 开发者
- 跨境业务、多语言内容运营团队
- 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
- 生产部署优先使用 Docker Compose 隔离依赖，并挂载 volume 持久化数据
- Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
- API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
- MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
- 容器内无法访问宿主机 localhost — 使用 host.docker.internal
- Docker：Chorus 提供官方镜像，docker compose up 一键启动
- CLI：直接 npm install -g / pip install，命令行调用
- 云端托管：可放在 Vercel / Railway / Fly.io 等 PaaS 平台
⚡ 核心功能
- 可视化 Agent 工作流编排，无需编写复杂代码
- 支持多步骤自动化任务链，实现全流程无人值守
- 与外部 API、数据库和第三方服务无缝集成
- 内置错误处理与自动重试机制，保障稳定运行
- 提供可复用的自动化模板，快速在同类场景部署
- 需要让 Claude / Cursor 操作本地工具的 AI 工程师
- 构建多智能体协作系统的 Agent 开发者
- 跨境业务、多语言内容运营团队
- 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
- 生产部署优先使用 Docker Compose 隔离依赖，并挂载 volume 持久化数据
- Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
- API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
- MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
- 容器内无法访问宿主机 localhost — 使用 host.docker.internal
👥 适合人群
🎯 使用场景
- 自动化日常重复性工作，将精力集中于创造性任务
- 构建数据采集 → 处理 → 输出的完整自动化管线
- 实现跨平台、跨系统的数据流转和业务协同
⚖️ 优点与不足
- +大幅减少重复性人工操作
- +可视化流程，清晰直观
- +可扩展性强，支持复杂场景
- −初始配置和调试需投入一定时间
- −强依赖外部服务的稳定性
- −复杂场景需具备一定技术基础
该工具使用 AGPL-3.0 协议，商用场景请仔细阅读协议条款，必要时咨询法律意见。
AI Skill Hub 为第三方内容聚合平台，本页面信息基于公开数据整理，不对工具功能和质量作任何法律背书。
建议在沙箱或测试环境中充分验证后，再部署至生产环境，并做好必要的安全评估。
⚠️ AGPL 3.0 — 最严格的 Copyleft，网络服务端使用也需开源，SaaS 使用受限。
🔗 相关工具推荐
❓ 常见问题 FAQ
经综合评估，Chorus Agent工作流 在Agent工作流赛道中表现稳健，质量优秀。如果你已有明确的使用需求，可以直接上手体验；如果还在评估阶段，建议对比同类工具后再做决策。
| 原始名称 | Chorus |
| 原始描述 | 开源AI工作流：The Agent Harness for AI-Human Collaboration, inspired by the AI-DLC (AI-Driven 。⭐841 · TypeScript |
| Topics | AI工作流Agent框架人机协作AI代理TypeScript |
| GitHub | https://github.com/Chorus-AIDLC/Chorus |
| License | AGPL-3.0 |
| 语言 | TypeScript |
收录时间：2026-05-17 · 更新时间：2026-05-19 · License：AGPL-3.0 · AI Skill Hub 不对第三方内容的准确性作法律背书。