codex-pair-pipeline vs DuDuClaw
codex-pair-pipeline is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
codex-pair-pipeline is a plugin bundle for AI coding tools published by Community Contributors. No marketplace we read lists it any more. DuDuClaw is an MCP server published by zhixuli0406. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  DuDuClaw | |
|---|---|---|
| Community marketplace gantisstorm/claude-code-pair-planning-framework | Removed on 2026-10-21 Version: 1.12.0 Forks (GitHub): 1 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.74.0 Downloads/month (npm): 4 505 Downloads/week (npm): 773 Forks (GitHub): 5 Stars (GitHub): 50 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.75.0 Downloads/month (npm): 4 505 Downloads/week (npm): 773 Forks (GitHub): 5 Stars (GitHub): 50 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | codex-pair-pipelineno longer listed · | DuDuClaw |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 6 | 50 |
| Forks (GitHub) (differs) | 1 | 5 |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (duduclaw) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/gantisstorm/claude-code-pair-planning-framework | github.com/zhixuli0406/duduclaw |
| Changes in the last 7 days (differs) | 4 | 5 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of codex-pair-pipeline
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Multi-agent autonomous building pipeline (Elira, Steven, Alba, David, Vex). Decomposes a goal into floors, builds real working code, validates and self-fixes.
-
Intelligent orchestration platform for AI coding tools. Coordinates Claude, Codex, Gemini, and OpenCode through a single MCP server — routing each task to the best model using…
-
Autonomous overnight coding agent. Queue tasks in YAML, run them via Claude CLI while you sleep, and use self-healing audit-fix loops to hit any quality target. Includes skills…
-
Drive Codeman from inside a Claude Code session: spawn worker sessions, prompt them, wait for them, read their answers, clean up. Acts only inside a Codeman-managed session.
-
Prevents subagent tech debt by injecting project architectural context (module boundaries, CLAUDE.md rules, conventions) into every subagent's prompt. Validates code placement and…
-
Feature-centric development framework for Claude Code — brainstorm, plan, build, and verify with structured workflows
What each says it does
codex-pair-pipeline
Multi-agent orchestration for complex coding tasks with Codex CLI (gpt-5.2). Scouts gather raw context, planners synthesize XML architectural instructions. Returns full plan with per-file instructions. Iterative discovery with user checkpoints and parallel execution. Session continuation via codex resume.
DuDuClaw
Local persistent memory and Markdown wiki for AI coding agents: 24 MCP tools, no gateway required.
How to run each
codex-pair-pipeline
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
DuDuClaw As a local MCP server: npm package
claude mcp add --env "DUDUCLAW_MCP_API_KEY=<YOUR_DUDUCLAW_MCP_API_KEY>" --transport stdio duduclaw -- npx -y duduclaw mcp-serverRequires: DUDUCLAW_MCP_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of codex-pair-pipeline publish no settings it asks for, so we do not compare settings.
What it can do: codex-pair-pipeline · What it can do: DuDuClaw · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.