ECC

Orchestrator · Last verified 2026-09-30

TL;DR

ECC, formerly Everything Claude Code, is an MIT-licensed catalog of subagents, skills, hooks, rules and a memory vault for coding agents, maintained by affaan-m. It targets Claude Code first, with a native Codex plugin and thinner adapters for OpenCode, Cursor and others. A hosted GitHub App is sold separately for private repositories.

Key facts

ECC key facts. Data as of 2026-09-30.
Type Orchestrator
Languages / SDKs JavaScript, TypeScript, Shell, Python
License MIT
Pricing model Open core
Orchestration pattern Other
GitHub stars 269,919 (as of 2026-09-30)
GitHub forks 40,339
Last push 2026-09-30
Latest release v2.2.1
Repository affaan-m/ECC
Website ecc.tools
Documentation github.com
Last verified 2026-09-30

Key features

  • The README lists 68 subagent definitions, 293 skills and 94 command shims, installed into Claude Code as the ecc@ecc plugin, alongside hooks and selectable rule packs. (source)
  • A guided installer and a native Codex marketplace plugin (codex plugin add ecc@ecc), plus per-harness install targets for Cursor, OpenCode, Gemini CLI, Zed, Hermes, OpenClaw, Kimi Code and others. (source)
  • Codex multi-agent support: sample explorer, reviewer and docs_researcher roles wired through features.multi_agent and [agents.<name>] in .codex/config.toml. (source)
  • The 2.0 release notes describe session adapters for Claude Code, Codex, OpenCode and dmux, a worktree lifecycle service for parallel agent worktrees, and an orch-* orchestrator skill family. (source)
  • Memory Vault: a local Markdown store under .ecc/memory/ with an ecc memory handoff command for passing context between harnesses, and an optional ecc-memory-mcp server. (source)
  • Hooks with selectable strictness profiles, including GateGuard checks on destructive shell commands before they run. (source)
  • AgentShield scans CLAUDE.md, settings, MCP configs, hooks, agent definitions and skills for secrets, permission and injection issues. (source)
  • A /plan command that restates requirements and waits for explicit user confirmation before any code is touched. (source)

Architecture and orchestration pattern

Pattern: Other

ECC is a content and tooling repository, not an agent runtime. The Claude Code plugin loads its Markdown subagent definitions, skills, commands and hooks; Node.js scripts handle installation, repair, sync and the ecc CLI. Each harness gets its own adapter, and the README's platform table rates them from stable (Claude Code) to instruction-only (GitHub Copilot).

Multi-agent work is delegated to the host. Subagents are definitions the host invokes; on Codex the sample roles run through Codex's own multi-agent feature and are steered with /agent. Claude agent files are not installed as Codex roles. The 2.0 notes add control-pane session adapters, a worktree lifecycle service that predicts conflicts between parallel agent worktrees, and orch-* orchestrator skills, but the README's file tree describes /orchestrate as 'prefer dmux-workflows or multi-workflow', and the README warns that Agent Teams cost extra tokens per teammate.

Memory is file-based. The Memory Vault keeps local Markdown under .ecc/memory/ (project and team) or ~/.ecc/memory/ (user), hooks distil sessions into summaries and learned instincts, and ecc memory handoff writes a note for another harness to recall. The vault is described as unreviewed context, not policy.

Human in the loop

Several checkpoints are documented. The /plan command must wait for explicit user confirmation before code changes, and /plan-canvas offers a browser-based annotate-and-approve review of the plan. GateGuard hooks gate destructive shell commands before they run, and Codex hooks need an explicit user trust decision. The installer previews each harness, destination and hook profile and asks for one final confirmation before writing. The README does not describe pausing or editing a running subagent beyond what the host harness provides.

Harnesses it can drive

Protocols

MCP, A2A and AG-UI support for ECC. See the full matrix.
ProtocolSupportNote
MCP Yes evidence
checked 2026-09-30
Server side: the package ships an optional, opt-in ecc-memory-mcp server exposing memory_save, memory_search, memory_read and memory_doctor, and a catalog of MCP server configs; the Claude plugin does not auto-enable them. No MCP client of its own.
A2A Unknown
checked 2026-09-30
README and MCP policy page do not mention A2A; repo code search returned only roadmap, payment-skill and release-script files that were not read as protocol support.
AG-UI Unknown
checked 2026-09-30
No AG-UI mention found in the README or repository code search; not checked against a listing in the AG-UI README.

Best for

  • Claude Code users who want a preinstalled set of review, build-repair, security and planning subagents plus hooks. (shortlist)
  • People running Claude Code and Codex side by side who want shared skills and a file-based handoff between them. (shortlist)
  • Auditing an existing agent setup (hooks, MCP config, permissions) with the bundled AgentShield scanner. (shortlist)
  • Solo developers who want TDD, review and verification steps enforced by hooks instead of prompts.

Not for

  • Users who need identical behaviour on every harness; the README rates only Claude Code as stable and calls most others beta, experimental or instruction-only.
  • Small-context or local-model setups with no tuning; the plugin advertises its installed catalog to the model and the README recommends selective installs when context matters.
  • Building agents in code; ECC has no SDK, only configuration content and CLI tooling for existing coding agents.

Quickstart

/plugin marketplace add https://github.com/affaan-m/ECC

Install not yet verified by this site. What this means

# Claude Code (inside the app): add the marketplace, then install the plugin
/plugin marketplace add https://github.com/affaan-m/ECC
/plugin install ecc@ecc
/plugin list ecc@ecc

# Plan a feature; the planner waits for your confirmation
/ecc:plan "Add user authentication with OAuth"

# Codex CLI, from a terminal
codex plugin marketplace add affaan-m/ECC
codex plugin add ecc@ecc
codex plugin list --json

# Cursor project adapter, from a clone of the repo
./install.sh --profile minimal --target cursor

Common pitfalls

  • Choose one install method per harness; stacking the Claude plugin with a manual install, or Codex sync with the Codex plugin, duplicates skills and hooks.
  • Claude Code plugins cannot distribute rules; copy the rule packs you want from rules/ by hand.
  • The README's guided setup pins npx ecc-universal@2.2.2 setup, but on 2026-09-30 the npm registry listed 2.2.1 as the latest version and no 2.2.2, so the pinned command may not resolve; the native plugin commands above do not depend on npm.
  • The Claude plugin does not auto-enable bundled MCP servers; add them manually.
  • Plugin hooks were silent no-ops on Node 21+ in early 2.0 builds (fixed in 2.0.0); the universal package needs Node.js 18 or newer and Claude Code 2.1 or newer for plugin setup.
  • Open issues report Claude Code warning about unknown keys in the bundled hooks.json.

Official quickstart

Pros

  • The README states plainly which harnesses are stable, beta, experimental or instruction-only, with a capability map, instead of claiming parity. (source)
  • MIT-licensed repository; the pricing page says the open-source toolkit stays free and the paid GitHub App sits on top of it. (source)
  • Install-state tracking with doctor, repair and uninstall commands, and a documented reset path for layered installs. (source)
  • MCP connector policy limits the default set to one server, chrome-devtools, and documents why six earlier defaults were retired. (source)
  • Frequent tagged releases with per-release notes under docs/releases. (source)

Cons

  • Large surface: the README says the Claude plugin advertises the whole installed catalog to the model and recommends selective installs when context footprint matters. (source)
  • Outside Claude Code support is partial: Cursor and OpenCode are beta adapters, and Hermes, OpenClaw and others are experimental or minimal. (source)
  • Counts in the README are inconsistent (68 and 67 agents appear in different sections), and its pinned npm version 2.2.2 was not on the npm registry when checked. (source)
  • Open issues report that hooks.json contains keys Claude Code does not recognise, causing an 'unknown keys ignored' warning on every session. (source)
  • Windows-native limitations are listed: continuous-learning observer daemon and memory-vault writes have open defects. (source)

Alternatives

FAQ

Does ECC support MCP?

It ships an optional ecc-memory-mcp server and a catalog of MCP server configs, and the Claude plugin leaves them disabled by default. It is not an MCP client and its default connector set is a single server, chrome-devtools.

Is ECC free?

The repository is MIT licensed and free to use. A hosted GitHub App, ECC Pro, is sold separately for private repositories; the pricing page lists Pro at $19 per seat per month, and the toolkit itself is not gated behind it.

Does ECC coordinate several agents itself?

Mostly no. It supplies subagent definitions, Codex role configs, worktree tooling and orchestrator skills, and the host harness runs the agents. Coordination features beyond that depend on the harness, such as Codex multi-agent mode.

Which harnesses does it install into?

Claude Code (plugin), Codex (native plugin), and install targets for OpenCode, Cursor, Gemini CLI, Zed, Hermes, OpenClaw, Kimi Code and others. The README rates Claude Code as stable primary and most others as partial.

What was it called before?

Everything Claude Code. The 1.x to 2.0 migration guide says the repository moved from affaan-m/everything-claude-code to affaan-m/ECC and the plugin id became ecc@ecc.

Sources

Unknown fields: protocols.a2a: no mention in the README or the MCP policy page; code search hits (roadmap docs, agent-payment-x402 skill, release script) were not read as A2A support. protocols.agui: no mention found. The README's guided setup command pins ecc-universal 2.2.2, which was absent from the npm registry on 2026-09-30 (latest 2.2.1, matching the GitHub release v2.2.1).

Something wrong or out of date, or do you maintain ECC and want this page removed? Report a correction or request removal.