openclaw-claude-code

MCP开发工具

提供方 Enderfga · 包名 openclaw-claude-code

开发工具 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopCursorClineClaude Code
查看接入方式

OpenClaw plugin — turn Claude Code CLI into a programmable, headless coding engine with plenty of tools, agent teams, and multi-model proxy

一句话选型结论

按资料字段整理

openclaw-claude-code 属于开发工具类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Cursor、Cline 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 314 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

openclaw-claude-code agent-teams ai-agent claude-code coding-agent

支持客户端

适用场景

openclaw-claude-codeagent-teamsai-agent

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
npx -y openclaw-claude-code

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Cursor、Cline,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
openclaw-claude-code当前 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Enderfga上游标注的维护方 Enderfga
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时openclaw-claude-code · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-04-11上游最后核验时间

详细介绍

11.8 KB
来自项目仓库与上游目录的原文,未做删改

Claw Orchestrator: A Unified Runtime for Coding Agent CLIs

📦 npm •
📖 Documentation •
🎬 Demo film •
📝 Changelog •
📚 Citation

Claw Orchestrator runs Claude Code, Codex, Antigravity, Grok Build, OpenCode and any
Agent Client Protocol agent (Kimi Code, dsh) as persistent sessions behind one API.
A run counts as done only when checks the agent did not write pass: you declare the checks, the runtime runs them
and reads the exit codes, and the evidence stays on disk. Runs are checkpointed workflows that survive a crash, and
every turn on every engine is recorded with its model, tokens and cost.

One bug, one acceptance contract, five engines, three runs each, first attempt only. The runtime ran the checks itself:
9 verified, 4 refuted, 2 errored (Grok Build hit its free-tier usage limit). One task, not a benchmark.
How the film was made, and how to re-run it.

The 40-second film, with sound

https://github.com/user-attachments/assets/5bf9bea8-e5ac-4632-a292-a80a45831dff

News

  • [2026-10] v7.16.0: clawo goal --engine claude runs a goal on Claude Code's /goal, with the same
    checkpointing, resume and verification as a Codex goal.
  • [2026-10] ResearchBoost-Agent, an autonomous agent
    that profiles, optimizes and validates AI training code, now runs its goal mode on Claw Orchestrator.
  • [2026-10] v7.14.0: any Agent Client Protocol agent runs as a session (engine: 'acp'), with presets for
    Kimi Code and dsh.
  • [2026-10] v7.13.0: clawo goal keeps a Codex /goal running for hours on one thread, reattaches it after a
    crash, and judges the result with your checks.
  • [2026-09] Declare, Compile, Look, built on Claw Orchestrator,
    was presented as a talk at the ECCV 2026 Workshop on Multimodal Digital Agents.
  • [2026-08] v6.0.0: the durable run kernel and the verification plane. A run survives its own process dying, and
    a run with an acceptance contract is judged by the runtime, not by the agent.

Highlights

  • ✅ Verdicts the agent cannot write: acceptance contracts (commands, HTTP probes, screenshots, diff policy, file
    assertions) run by the runtime. A run ends verified, refuted or unverified, and editing the tests its contract
    runs refutes it (guide).
  • 🔀 Many vendors, one API: Claude Code, Codex, Antigravity, Grok Build, OpenCode, any ACP agent and custom CLIs.
    clawo fanout asks several at once; session_handoff moves a live conversation to another engine in the same
    workspace (guide).
  • 💾 Survives a crash: every state transition is checkpointed; resume, retry, timeout, cancel and steer come from
    the kernel (guide).
  • 🎯 Long goals: clawo goal runs a Codex /goal unattended on one thread, resumes it after usage limits within a
    bound, optionally inside your own sandbox (guide).
  • 💰 Known cost: one per-turn ledger across engines (clawo runs) and a maxBudgetUsd cap the runtime enforces on
    every engine (guide).
  • 🔌 Fits your tools: a CLI, an MCP server, an ACP agent for editors, an OpenAI-compatible endpoint, a TypeScript
    SDK and an OpenClaw plugin (ways to run).

claude-squad, Conductor and Vibe Kanban are interfaces for running agents side by side in worktrees; Claude Code
subagents and Codex's parallel attempts stay within one vendor. Claw Orchestrator is a headless runtime underneath:
several vendors behind one API, durable workflows, and a verification step the agents cannot edit. They can be used
together.

Quick Start

Requires Node 22+ and at least one engine CLI installed and logged in (claude, codex, agy, grok or opencode).```bash
npm install -g @enderfga/claw-orchestrator
clawo serve & # local runtime + dashboard on 127.0.0.1:18796
bash clawo solve "The test fails. Fix price.js." --engine codex \ --check "npm test" --check "node ../holdout/price.spec.mjs" --wait clawo verify <runId> # each check, why it failed, the files that changed clawo runs --since 1h # every turn on every engine: model, tokens, cost, verdictbash
clawo fanout "How would you speed up this test suite?" --engines claude,codex,grok --synthesize --wait
clawo goal --objective-file GOAL.md --check "npm run bench:check" --check-timeout 120 --wait


The server writes an access token to `~/.openclaw/server-token` and the CLI reads it from there. To sign in the
browser once, open `http://127.0.0.1:18796/login?token=&redirect=/dash`.

- 🧪 **Acceptance contracts and evidence bundles** (guide)
- 🔁 **Workflows, resume and the goal node** (guide)
- 🖥️ **Every CLI command** (guide)
- 🧰 **All 78 tools** (guide)

## Ways to run

For · Start here
**CLI and dashboard** · Terminals and scripts · `clawo serve`, then `cli.md`
**MCP server** · Claude Code, Claude Desktop, Cursor, Cline, Continue, Zed, Windsurf, Goose, Hermes Agent · `claude mcp add clawo -- clawo-mcp`, then `mcp.md`
**ACP agent** · Zed, JetBrains, Neovim, Emacs, the VS Code ACP extension, dsh · `clawo acp`, then `acp.md`
**OpenAI-compatible endpoint** · Any OpenAI SDK client or webchat, without changing call sites · `POST /v1/chat/completions` (`openai-compat.md`)
**TypeScript SDK** · Embedding the runtime in your own service · `import { SessionManager } from '@enderfga/claw-orchestrator'` (below)
**OpenClaw plugin** · Every OpenClaw agent gets all 78 tools · `curl -fsSL https://raw.githubusercontent.com/Enderfga/claw-orchestrator/main/install.sh \ · bash````ts
import { SessionManager } from '@enderfga/claw-orchestrator';

const manager = new SessionManager();
await manager.startSession({ name: 'fix-tests', engine: 'claude', cwd: '/project' });
const result = await manager.sendMessage('fix-tests', 'Fix the failing tests');

From an MCP host, ask for workflow_start with template solve, a task, and a contract such as
{"checks":[{"type":"command","cmd":"npm","args":["test"]}]}. In an ACP editor, the model selector is grouped by
engine, so one dropdown switches between Claude, Codex, Antigravity and Grok models mid-session.

Engine compatibility

Engine CLI Tested version
Claude Code claude 2.1.310
Codex codex 0.164.0
Antigravity agy 1.4.6
Grok Build grok 1.0.70
OpenCode opencode 1.19.4
ACP agent any Kimi Code 2.3.1, dsh 0.2.1-rc.2
Custom CLI any —

An agent that serves the Agent Client Protocol on stdio runs as
engine: 'acp'; any other coding CLI that runs as a
subprocess can be wired up as a custom engine.

How the table stays current

The versions above are what the weekly sweep last ran. scripts/sweep.ts measures each core engine's installed,
pinned and upstream version, diffs the flags the wrapper passes against the binary's --help, runs one live turn
through the real wrapper class, smokes the ACP and MCP entry points, and checks src/models.ts against the
OpenAI, Anthropic and xAI published price tables. It contains no model call, so the check that reports a wrapper as broken does not
share the wrapper's failure modes.

scripts/sweep-workflow.json wraps the same script as a durable run on this project's own kernel: verifier → router
→ an agent that drafts the alignment on a sweep/ branch → a human gate. A person reviews and merges; the
orchestrator does not edit its own code unattended.

All features

Capability What it does Reference
Persistent sessions Long-lived agents kept alive across requests, with context, tool, model and worktree control. sessions.md
Multi-engine runtime One interface over the engines above, any ACP agent, and custom CLIs. multi-engine.md
Session handoff Moves a live conversation to another engine or model in the same workspace; the old session keeps running. sessions.md
Verification plane Acceptance contracts the runtime runs itself, with an evidence bundle on disk; a run without a contract ends unverified. verification.md
Durable run kernel Declarative workflows over agent, goal, fanout, council, verifier, human_gate, router and more, checkpointed. workflow.md
Fan-out One task across N engine/model agents in parallel, with an optional synthesis pass. tools.md
Council Parallel agents in isolated git worktrees, voting until they reach consensus. council.md
Autoloop A Planner, Coder and Reviewer iterating on a workspace, each with its own engine and model; you chat with the Planner. autoloop.md
Ultraapp A short structured interview turned into a deployed web app at localhost:19000/forge//. ultraapp.md
ultracode session_start({ ultracode: true }) lets Claude orchestrate a dynamic workflow of subagents. tools.md
Run ledger, spend caps Every turn on every engine in one JSONL ledger (clawo runs), and a maxBudgetUsd cap enforced on every engine. observability.md
OpenAI-compatible proxy POST /v1/chat/completions routed to persistent sessions on the engine the model name selects, streamed back in OpenAI shape. openai-compat.md
Dashboard Autoloop, Council and Forge tabs with lifecycle controls and live event streams, and a Runs tab of durable workflow runs. dashboard.md

Built on Claw Orchestrator

  • ResearchBoost-Agent: an autonomous agent that profiles,
    optimizes and validates AI training code; its long goal-mode runs use clawo goal
    (blog).
  • Declare, Compile, Look: coordinate-free layout generation with
    vision-in-the-loop repair, ECCV 2026 Workshop on Multimodal Digital Agents (talk).

Using Claw Orchestrator in a project or paper? Open a pull request to add it here.

Citation

If Claw Orchestrator helps your research, please cite it:```bibtex
@misc{fang2026claworchestrator,
title = {Claw Orchestrator: A Unified Runtime for Coding Agent CLIs},
author = {Fang, Guian},
year = {2026},
howpublished = {\url{https://github.com/Enderfga/claw-orchestrator}}
}


Research built on Claw Orchestrator:```bibtex
@misc{researchboost2026infra,
  author = {{ResearchBoost Team}},
  title  = {{ResearchBoost}: {RSI} starts with Infra},
  year   = {2026},
  url    = {https://ydove0324.github.io/hx_resume/blog/researchboost/}
}

@inproceedings{fang2026declare,
  title     = {Declare, Compile, Look: Coordinate-Free Layout Generation with Vision-in-the-Loop Repair},
  author    = {Fang, Guian and Liu, Mengsha and Shou, Mike Zheng},
  booktitle = {ECCV 2026 Multimodal Digital Agents Workshop},
  year      = {2026},
  url       = {https://openreview.net/forum?id=Romd50Ce0w}
}

Contributing

See CONTRIBUTING.md. Run npm run build && npm run lint && npm run format:check && npm run test
before submitting.

License

MIT, see LICENSE.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
openclaw-claude-code 怎么安装?

在客户端按下面的安装命令接入:npx -y openclaw-claude-code。对应的包名是 openclaw-claude-code。装完在客户端配置里引用同一个包或端点。

openclaw-claude-code 怎么在 Claude Desktop、Cursor、Cline 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

openclaw-claude-code 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

openclaw-claude-code 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

openclaw-claude-code 支持哪些客户端?

资料标注支持 Claude Desktop、Cursor、Cline、Claude Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

openclaw-claude-code 能提供哪些能力?

资料显示能力标签包括 openclaw-claude-code、agent-teams、ai-agent、claude-code、coding-agent。具体工具清单以官方文档为准。

openclaw-claude-code 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

openclaw-claude-code 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-04-11。