mco

mco-orgMIT活跃维护

命令行驱动的 AI 编码代理编排工具,能并行运行多个代理和模型、对比原始回答,并协调代码审查与实现流程。

CLI-first orchestration for AI coding agents: run selected agents and models in parallel, compare raw answers, and coordinate review or implementation workflows.

v0.13.0发布于 2026-11-07 00:22 UTC554star +1 / 7 天60fork同步于 2026-11-10 17:58 UTC

怎么上手

由 README 提炼,执行前请确认
npx @tt-a1i/mco@latest install
mco doctor --json
硬件要求按 README 说明

README 未说明;MCO 本身是 CLI 编排层,实际算力由各 provider CLI 及其模型决定

下载:源码 zip·GitHub Releases(安装包)本站不镜像安装包

项目说明

由 README 自动翻译提炼

把多个 AI 编码 agent 并行跑起来,对比原始答案再决定怎么做

命令行驱动的 AI 编码代理编排工具,能并行运行多个代理和模型、对比原始回答,并协调代码审查与实现流程。

核心能力

  • 显式指定 provider 并行分发同一任务
  • 保留每次调用的完整原始答案与运行状态
  • 支持 chain 链式执行与 artifact 文件传递
  • 用 --divide 按文件或维度切分审查范围
  • 内置 12 种 provider 适配器,单个失败不影响其他结果

容易踩的坑

各 provider CLI 需自行安装并完成认证,MCO 不代管;不传 --providers 或 --agent 时不会自动推断团队,需配置默认或显式指定;--allow-paths 只校验请求范围,不是操作系统级沙箱

内容由模型根据 README 生成,可能不完整或不准确,以官方文档为准。看原文 README

最近发版

5 个版本v0.13.0
  1. v0.13.0最新正式版2026-11-07 · 2026-11-07 00:22 UTC

    v0.13.0 - Kimi Code and current Agent CLIs

    MCO now supports Kimi Code CLI and updates its integrations for the current Antigravity, Pi, OpenCode, Hermes, Codex, and Grok CLIs.

    Highlights

    • Added Kimi Code 2.5.2 support, including packaged read-only/write tool profiles, model selection, JSONL answers, and file-backed chain, debate, and synthesis stages.
    • Updated OpenCode 2 command arguments and model selection, Hermes context controls, and Antigravity/Grok permission modes.
    • Preserved Pi/Hermes model-provider routing across CLI, MCP, and multi-stage runs.
    • Corrected false-success handling for Pi errors and truncation, Codex nonzero exits, and Grok headless permission refusals. JSONL answers preserve Unicode line and paragraph separators.

    Compatibility notes

    • OpenCode 2 no longer supports the previous plugin-isolation mechanism. Requests for it fail in strict mode or are dropped in best-effort mode.
    • A Pi provider override must include a model. Hermes context-file disabling uses --ignore-rules, which also disables memory and preloaded skills.
    • Read-only debate and synthesis reject providers that cannot enforce a read-only mode. Hermes requires explicit yolo execution.
    • Kimi profiles restrict tools; they do not create an OS sandbox or disable installed hooks. Kimi uses the shim fallback with --transport acp.
    • Grok's headless permission-refusal diagnostic marks the invocation as failed, including a run that later recovered with another tool.

    Validation

    Antigravity, Pi, Kimi, Codex, and Grok completed real file-read and file-write tasks. Codex→Kimi chain and Kimi debate/synthesis also passed. OpenCode inference was blocked by credentials or exhausted free quota; Hermes was blocked by its configured local model endpoint. Claude Code was excluded from live calls.

    The automated suite passed 526 Python tests and 19 Node tests, with three platform-specific skips. Package build/install checks passed. See the dated compatibility matrix for audited CLI versions and verification limits.

    Install or upgrade

    npm install -g @tt-a1i/[email protected]
    mco --version
    

    Python 3.10+ is required on PATH. MCO is published through npm only.

  2. v0.12.12026-10-07 · 2026-10-07 10:58 UTC
    查看更新说明

    MCO v0.12.1 adds Antigravity CLI support and publishes the Windows, MCP, and Ollama reliability fixes merged since v0.11.0.

    Added

    • Built-in Antigravity CLI (agy) adapter with model selection, execution modes, authentication checks, and permission-risk reporting (#127).
    • MCP progress notifications during long runs and per-call timeout overrides (#125).

    Fixed

    • Install locked Node dependencies before the release tests. The initial v0.12.0 release attempt failed before npm publication; v0.12.1 includes the same product changes with the corrected publish workflow.
    • Windows npm/Python command-shim execution and Python runtime compatibility (#123, #124).
    • MCP calls now honor configured timeouts, whole-run deadlines, parallelism limits, and pinned models (#125).
    • Provider answers survive legacy console encodings instead of disappearing (#125).
    • Ollama readiness checks resolve the exact requested model and treat flag-like names as positional arguments (#128, #129).

    Update

    npm install -g @tt-a1i/[email protected]
    mco --version
    

    Full changelog: https://github.com/mco-org/mco/compare/v0.11.0...v0.12.1

  3. v0.11.02026-07-29 · 2026-07-29 15:15 UTC
    查看更新说明

    v0.11.0 - Invocation-native runtime

    Status: breaking release guidance

    This release changes MCO from a findings/decision pipeline into a raw-answer invocation runtime. Legacy findings-driven design documents remain available for context but are superseded by the invocation runtime v1 contract; this note is the migration guide for callers adopting the new public surface.

    New behavior

    • Use repeatable --agent [alias=]provider:model for explicit Agent identity and multiple models from one Provider.
    • Use --providers as the invocation-native shorthand for one configured/default model per Provider.
    • Consume raw answer text plus operational invocation records. Task status is complete, partial, or failed, with exit codes 0, 1, and 2.
    • Use text mode, --json, or --stream jsonl; stdout contains answers or the selected machine protocol, while diagnostics go to stderr.
    • Use --chain, --debate, and --synthesize for LLM-driven file-backed stages.
    • Use --result-mode artifact|stdout|both for temporary or persistent Markdown artifacts.
    • A synthesis manifest retains run and debate records, including failures or missing entries, but never includes synthesis itself. Root result.md groups actual stages, places synthesis first, and keeps every original answer and failure record.

    Breaking removals

    The following surfaces are removed:

    • mco findings and the findings JSON schema;
    • semantic normalization, deduplication, confidence, consensus, passive lifecycle, and findings-driven memory runtime;
    • Markdown-PR and SARIF renderers;
    • content-based INCONCLUSIVE status;
    • --format, --strict-contract, --memory, --space, --diff, --staged, --unstaged, and --diff-base.

    Removed flags return migration guidance rather than being silently ignored.

    Migration examples

    Old structured review callers should send the desired scope and output shape as a raw prompt:

    mco review --target-paths runtime --providers claude,codex \
      --prompt "Review runtime/ for correctness and security risks; report your reasoning in natural language." \
      --result-mode both --task-id runtime-review
    

    Old multi-model callers should use explicit invocations:

    mco run --prompt "Compare these implementations." \
      --agent fast=pi:model-a \
      --agent careful=pi:model-b \
      --stream jsonl
    

    Old persistent-memory callers should save and pass Markdown artifacts through chain/debate/synthesis stages:

    mco run --prompt "Analyze the repository." \
      --providers claude,codex --chain --execution-mode read_only \
      --result-mode artifact --task-id repository-analysis
    

    Write safety

    MCO does not create or manage worktrees. If a user explicitly chooses parallel writers, the calling Agent must partition non-overlapping --target-paths and warn about overlapping edits.

  4. v0.10.82026-07-10 · 2026-07-10 07:48 UTC
    查看更新说明

    What's Changed

    New Contributors

    Full Changelog: https://github.com/mco-org/mco/compare/v0.10.6...v0.10.8

  5. v0.10.32026-06-27 · 2026-06-27 08:24 UTC
    查看更新说明

    Fixed

    • Concatenate multi-part JSONL text_delta streams in event order for run-mode final text extraction.
    • Pass --dir <repo_root> to OpenCode so review/run tasks inspect the selected repository.

    Changed

    • Clarify that MCO defaults to the audited five providers while supporting seven providers explicitly.
    • Mark Hermes as an explicit elevated opt-in provider because Hermes oneshot mode auto-bypasses approvals.
    • Expand manual capability probes and step5 benchmark defaults to include Hermes and Pi.

    Validation

    • PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s tests -p 'test_*.py' -> 696 tests OK
    • GitHub Gate on PR #89 -> success
    • npm pack --dry-run --json -> 0.10.3 pack OK
    • local npm install smoke -> Pi run returned OK
    • live 5-provider run/review smoke -> claude/codex/opencode/hermes/pi all succeeded; review parse/schema valid for all 5

用户点评

登录用户的真实使用记录,可按版本和硬件筛选
共 0 条

    还没有人点评。第一个说出真实体验的人最有价值。

    README 原文

    未翻译

    MCO is a lightweight, CLI-first orchestration layer for AI coding agents. Give one task to the agents and models you choose, run them in parallel, and compare their raw answers before you act.

    Use MCO for code review, implementation, architecture analysis, CI checks, and any workflow where one model's blind spots matter.

    It works from a terminal or from another coding agent such as Claude Code, Codex, Cursor, Copilot, Pi, or OpenClaw.

    MCO is actively maintained. For a browser workbench with persistent agent identity and a shared task graph, see Hive.

    Quick start

    Install the CLI and its bundled mco-cli Skill:

    npx @tt-a1i/mco@latest install
    

    Check the agents available on your machine:

    mco doctor --json
    

    Run a read-only multi-agent review:

    mco review \
      --repo . \
      --prompt "Review this repository for high-risk bugs." \
      --providers claude,codex,pi
    

    Run a coding task with workspace write access:

    mco run \
      --repo . \
      --prompt "Implement the requested change and run the relevant tests." \
      --providers codex,pi \
      --execution-mode write
    

    MCO never infers a provider/model team from detected binaries. If neither --providers nor --agent is supplied, a top-level providers config entry is used as the saved default; without one, the team must be selected explicitly. A calling agent should still show and confirm the resolved provider/model team with the user before dispatch.

    Why MCO

    One agent gives you one perspective. MCO turns selected agents into a review or execution team:

    1. Choose — explicitly select the agents for the task.
    2. Dispatch — run them in parallel, chain their work, or divide the scope.
    3. Compare — retain each invocation's complete raw answer and operational status.
    4. Decide — inspect evidence, disagreements, and failures before acting.

    MCO keeps answer text opaque. It does not turn natural-language output into findings, severity, confidence, consensus, or an automatic decision.

    For explicit review coordination, --perspectives-json adds a Provider-specific prompt focus. --divide files excludes ignored/local/build directories and round-robins the remaining sorted repository files without overlap, while --divide dimensions rotates review lenses in declaration order without changing target paths. These choices are visible in dry-run and arrange only the prompt or scope; the returned invocation answers remain raw.

    Built-in providers

    ProviderCLIProvider ID
    Claude Codeclaudeclaude
    Codex CLIcodexcodex
    Gemini CLIgeminigemini
    OpenCodeopencodeopencode
    Qwen Codeqwenqwen
    GitHub Copilot CLIcopilotcopilot
    Hermeshermeshermes
    Pipipi
    Grok Buildgrokgrok
    Cursor CLIcursor / agentcursor
    Antigravity CLIagyagy
    Kimi Code CLIkimikimi

    Each provider CLI remains responsible for its own installation, authentication, model access, and native sandbox behavior.

    Common workflows

    GoalCommand
    General multi-agent taskmco run --providers claude,codex --prompt "..."
    Thin raw-answer code reviewmco review --providers claude,codex --prompt "..."
    Compare multiple modelsmco run --agent fast=pi:model-a --agent careful=pi:model-b --prompt "..."
    Preview without executionmco review --providers claude,pi --dry-run --json
    Live terminal progressmco review --providers claude,codex --stream live
    Machine-readable eventsmco review --providers claude,codex --stream jsonl
    File-backed chainmco run --agent first=pi:model-a --agent next=pi:model-b --chain --result-mode artifact
    Debate and synthesismco review --providers claude,codex --debate --synthesize --result-mode both
    Discover provider modelsmco agent models --providers codex,pi --json

    Pin models for one run without changing provider CLI defaults:

    mco review \
      --providers codex,pi \
      --provider-models-json '{"codex":"gpt-5.4","pi":{"provider":"seal","model":"deepseek-v4-pro"}}' \
      --prompt "Review this repository for bugs."
    

    Permissions and safety

    MCO translates one execution profile into each provider's native flags:

    ModeIntended useDefault
    read_onlyInspect and review without workspace mutationmco review
    writeCreate and edit workspace filesmco run
    yoloUse the provider's broadest bypass profileExplicit opt-in only

    Important boundaries:

    • --allow-paths validates MCO's requested scope; it is not an operating-system sandbox.
    • Provider sandbox strength depends on the underlying CLI.
    • Hermes oneshot bypasses approvals and therefore requires explicit --execution-mode yolo.
    • ACP terminal access is a trusted-agent capability. Use isolation for untrusted agents or prompts.
    • MCO does not create or manage worktrees. If the user selects parallel writers, partition ownership with non-overlapping --target-paths and warn about edit conflicts.

    See Provider and permission reference for the complete mapping.

    Use MCO from another agent

    MCO's CLI is self-describing. A calling agent can read mco -h, resolve saved defaults, confirm the provider/model team with the user, preview the policy, and then execute.

    “Use MCO to run a security review with Claude and Codex, and an architecture review with Pi.”

    The installer and runtime use two different selections:

    • Installer --agent chooses which calling agents receive the MCO Skill.
    • Runtime --providers, saved providers config, or runtime --agent declarations choose the task invocations.
    npx @tt-a1i/mco@latest install --agent codex --agent claude-code --yes
    mco doctor --skill-health --json
    

    How it works

    You or a calling agent
            │
            ▼
      mco run / review
            │
            ├── Claude ──┐
            ├── Codex    │
            ├── Gemini   ├──► raw answers / file-backed stages ──► output
            ├── Pi       │
            └── ...   ───┘
                                  │
                           text · JSON · JSONL · Markdown artifacts
    

    Provider processes are isolated behind a shared adapter contract: detect, run, poll, cancel, and transport decode. One invocation failure does not discard successful provider answers.

    Documentation

    TopicGuide
    Installation, first run, and common workflowsWorkflow guide
    Providers, models, and permission mappingsProvider reference
    CLI flags, outputs, artifacts, and exit codesCLI reference
    Config files and custom agentsConfiguration reference
    Machine-readable error contractError contract
    Invocation and artifact contractInvocation contract
    Provider permission contractPermission contract
    Release processRELEASING.md
    Release historyCHANGELOG.md

    Run mco <command> --help for the authoritative option list installed with your version.

    Development

    git clone https://github.com/mco-org/mco.git
    cd mco
    python3 -m pip install -e .
    python3 -m unittest discover -s tests -p 'test_*.py'
    npm test
    

    License

    MIT — see LICENSE.