Quick Verdict
ECC, short for Everything Claude Code, is not a coding model or a standalone IDE. It is a distribution and operating layer for agents, skills, rules, hooks, MCP configuration, and engineering workflows across coding-agent harnesses. Its current stable line is v2. The project says it supports Claude Code, Codex, Cursor, OpenCode, Gemini, Zed, GitHub Copilot, and other environments. The repository is MIT licensed, while ECC Tools and ECC Pro are separate hosted commercial surfaces. Free source code therefore does not mean every private-repository audit or cloud feature is free.
ECC is most useful for experienced developers who switch among multiple agents, can review configuration changes, and want repeatable testing, security, research, or orchestration workflows. It is a poor fit for anyone expecting a harmless prompt pack. A broad installation can write agents, skills, rules, commands, and hooks into user or project directories. Some workflows can execute shell commands, inspect repositories, or connect to MCP services. Preview the plan, install selected modules, pin a reviewed commit, and expand permissions gradually.
Best For
- Developers who use Claude Code, Codex, or OpenCode and want shared workflow conventions.
- Platform teams able to review shell scripts, Node.js utilities, permission declarations, and configuration diffs.
- Small engineering teams standardizing security review, verification loops, session records, or worktree orchestration.
- Not ideal for locked-down terminals, teams unable to audit third-party hooks, or users seeking zero-configuration assistance.
Key Features
- Cross-harness packaging: one repository contains adapters and configuration surfaces for several coding agents.
- Skills and agents: reusable workflows cover coding standards, testing, security, research, deployment, and orchestration. Treat catalog counts as changeable project metadata.
- Rules and hooks: rules add persistent context; hooks can run checks or record state around session and tool events.
- v2 operator layer: project documentation describes session adapters, MCP inventory, worktree lifecycle management, and control-pane workflows.
- AgentShield: a separate npm surface scans secrets, permissions, hooks, MCP configuration, and agent definitions; model-assisted scans can incur model charges.
- Install lifecycle: plan/apply tooling, installed-state tracking, doctor, repair, and dry-run uninstall make file changes more governable.
- Hosted services: ECC Tools provides a GitHub App surface, while ECC Pro targets private repositories. Their access and billing are separate from the MIT repository.
Use Cases
- Install only common rules and the language packs a project needs instead of loading the entire catalog.
- Invoke planning, code review, verification, and security workflows as reusable skills.
- Carry similar conventions between Cursor, Codex, and OpenCode while testing each harness adapter independently.
- Use list-installed, doctor, repair, and uninstall dry-run commands to account for ECC-managed files.
- Evaluate the hosted GitHub App only when remote PR audits are needed, with separate review of repository permissions.
Pricing
| Surface | License or billing | Intended use |
|---|---|---|
ECC v2 repository / ecc-universal | Free, MIT | Local agents, skills, rules, hooks, and CLI |
| AgentShield CLI | Open-source tool; model usage may cost extra | Local or CI configuration scans |
| ECC Tools GitHub App | Project offers free and paid surfaces | Hosted PR auditing |
| ECC Pro | Project advertises per-seat subscription | Private repositories and hosted features |
Plans, quotas, and included capabilities can change, so confirm them on ecc.tools/pricing and the GitHub App listing. Claims about time savings, security-test counts, catalog size, or popularity come from project-maintained materials. They are useful context, not an independent audit or performance guarantee.
Pros
- The local source is MIT licensed and can be inspected, forked, and reduced to selected modules.
- Cross-harness packaging helps teams preserve methods rather than rewrite one-off prompts.
- Preview, state, repair, and uninstall tooling is more manageable than copying unrelated configuration snippets.
- The v2 design groups sessions, MCP inventory, worktrees, and operator controls into a coherent workflow layer.
- Official documentation explicitly warns against stacked installation methods and discusses security scanning.
Cons
- A full installation is invasive: it can modify multiple user and project configuration locations, and hooks execute automatically.
- A large catalog of skills, agents, and compatibility shims can consume context and create duplicated behavior.
- Harness permission systems differ, so cross-harness support does not mean exact feature parity.
- The hosted Pro and GitHub App promises must be evaluated separately from the MIT repository.
- Following
main,latest, or an unpinned installer increases supply-chain and behavior-drift risk.
Alternatives
| Tool | Best for | Difference from ECC |
|---|---|---|
| Claude Code | A focused terminal agent | Official product with a narrower surface, not a cross-harness config library |
| Codex | OpenAI coding workflows | Provides its own runtime; ECC components still need adapter review |
| OpenCode | Users wanting an open agent client | It is a client, while ECC is primarily a workflow and configuration layer |
| Cursor | Visual AI IDE users | Faster IDE onboarding but less cross-client governance |
| GitHub Copilot | Enterprise IDE and GitHub users | Mature managed service with different customization and hook boundaries |
FAQ
Is ECC v2 free?
The ECC repository and ecc-universal package are MIT licensed and free to use or modify. ECC Pro and some hosted GitHub App capabilities are separate commercial surfaces. Model APIs, CI, and third-party MCP services may also charge independently.
What files can ECC modify?
The answer depends on the installer and profile. It can touch agent, skill, rule, command, hook, MCP, and install-state locations at user or project scope. Inspect the install plan or dry-run first, and do not combine a plugin installation with a full manual profile.
Why is the installation considered invasive?
Rules alter persistent model context, hooks can execute scripts on events, skills and agents add callable behavior, and permission settings may grant shell, filesystem, or network access. Those are functional capabilities, but each should be enabled with least privilege.
Should a production setup pin an npm version or a commit?
Pin an exact npm version at minimum. For GitHub-based installation, use a reviewed release tag and record the full commit SHA when stronger provenance is required. Avoid silently tracking latest or main in production.
Are ECC’s security and productivity claims independently verified?
Treat star counts, test counts, catalog totals, and productivity statements in the README as project-attributed claims. They are not substitutes for reviewing hooks, running your own tests, or checking whether AgentShield rules match your threat model.
Bottom Line
ECC v2 is valuable as a reusable workflow layer across coding-agent harnesses, not as another chat box. Teams with configuration governance may save repeated setup work. New users can instead inherit duplicate hooks, broad permissions, and upgrade drift. Decide between local OSS and hosted services first, select one installation path, preview every write, pin a version or commit, and grant only the modules and permissions you need.