
If you use an AI coding agent, you’ve probably typed the same instructions over and over: write a plan first, add tests, review your own work. ECC is an open-source project that tries to bake that process in once, so you don’t rebuild it in every prompt. This guide covers ECC for Claude Code and its sibling tools, what it does well, and where it falls short.
One caveat up front. The README excerpt I was given cuts off before the exact install commands, so I won’t print any. I’ll tell you what the README says about installing and where to find the commands.
What is ECC?
ECC (the repository is affaan-m/ECC) describes itself as “the agent harness performance optimization system.” An agent harness is the tool that runs an AI model as a coding assistant in your terminal or editor, for example Claude Code, Codex, Opencode or Cursor. ECC adds skills, instincts, memory, security and what it calls research-first development on top of those tools.
The README’s pitch is that your agent can already write code, but ECC gives it a coordinated engineering system and toolbox. The workflow it promotes looks like this:
plan -> test -> implement -> review -> verify -> remember -> improve
Its motto, also from the README: “Optimize the context window. Persist everything else.” The context window is the amount of text a model can keep in mind at once, so the idea is to store durable knowledge outside it.

Why it might be useful
According to the README, ECC aims to make an agent do the following:
- Plan before it builds.
- Verify changes with tests.
- Review its own work from a fresh context.
- Remember what matters between sessions.
- Turn repeated wins into reusable skills and workflows.
Think of a freelancer or a small dev team that leans on an AI agent for everyday work. Without a shared process, quality swings with how well you phrase each prompt. A harness like this is meant to make the good habits the default. That’s the project’s claim, and I haven’t run it, so treat it as the intended benefit rather than a measured result.

Key features
- Skills and memory. The repo description lists skills, instincts and memory as core pieces, plus a security focus.
- Multiple harnesses. The README says it works best with Claude Code today, has native Codex and Qoder plugin paths, and a single maintainer ships weekly across 7 harnesses.
- A curated profile. The v2.2.3 release notes describe a
pi/coreprofile with 123 curated skills and 24 prompt commands. - Companion npm packages. The README names
ecc-universalandecc-agentshieldas official packages. - A GitHub App. ECC Tools is a GitHub App you can install free. Private repositories need ECC Pro, listed at $19 per seat per month on the project’s pricing page.
The basics: licence, popularity, freshness
ECC is MIT-licensed, a permissive open-source licence, and the README says the repository stays MIT “forever.” It’s written mainly in JavaScript. GitHub shows about 306,900 stars and 45,200 forks, with 181 open issues. The repo was created on January 18, 2026, and its last recorded activity was November 17, 2026. The latest release in the notes is v2.2.3, published October 1, 2026.
That release was mostly housekeeping. It standardized the project name to ECC in the pi/core profile and fixed a release-workflow problem. In 2.2.2, the workflow gave up after about 30 seconds while npm was still processing an upload, so the run failed. Now it polls for up to five minutes.
How to install ECC for Claude Code
The README offers two routes for Claude Code: a guided setup, or native plugin commands. Both install the same plugin, ecc@ecc. The README’s advice is to choose one and not stack a full manual Claude install on top of it.
The exact commands live in the README’s “Install ECC” and “Claude Code details” sections, which weren’t in my excerpt. Copy them from the repository rather than from a third-party post, mine included.
On platforms: the notes name Claude Code, Codex, Opencode and Cursor, and the README mentions Qoder. They don’t say which operating systems are supported, so check the README before you commit.
A security note worth reading
The README carries a warning: install ECC only from official channels. Those are the GitHub repository, the npm packages ecc-universal and ecc-agentshield, the GitHub App, the plugin slug ecc@ecc and the website ecc.tools. The project says third-party re-uploads and unofficial mirrors aren’t reviewed and may contain malware. With a repo this popular, copycats are a fair worry.
Limitations and who should skip it
This is our take, based on the notes rather than hands-on testing.
- It’s tuned for Claude Code. The README says it works best there. Other tools get native paths or what the README calls capability-led support, but expect a different experience.
- It’s a lot of machinery. Skills, memory, commands and security layers mean more to learn and more that can go wrong. If you only use an AI assistant for occasional snippets, a plain prompt may serve you better.
- One maintainer. The README describes a single maintainer shipping weekly. That’s impressive pace, but it’s also a dependency risk for a team building a workflow around it.
- Some features are paid. The open-source repo is free, but private repos with the hosted GitHub App need ECC Pro.
- Issue volume. 181 open issues isn’t alarming for a project this size, but expect rough edges.
- Unverified claims. The notes include no benchmarks showing it improves output quality. Judge it on your own projects.
Skip it if you don’t use an agent harness at all, if you want a tiny single-purpose tool, or if you can’t audit third-party code that runs inside your coding environment. Reading what a plugin does before installing it is good practice here.
FAQ
Is ECC free?
The repository is MIT-licensed and free. The hosted GitHub App can be installed free, while private repositories start at $19 per seat per month with ECC Pro, according to the README.
Does ECC work with Claude Code?
Yes. The README says it works best with Claude Code today and installs as the ecc@ecc plugin.
Does it work with Codex or Cursor?
The repo description names Codex, Opencode and Cursor. The README mentions native Codex and Qoder plugin paths. Check the README for the current level of support on each.
Where do I get the official version?
Use the GitHub repo, the two npm packages named above, the GitHub App or ecc.tools. Avoid mirrors.
What to do next
Open the README, read the install section for your tool, and pick a single route. Try it on a small, low-stakes project first and see whether the plan, test and review loop actually saves you time. Alternatives aren’t covered in the notes I had, so I won’t name any. Start with the repository and the official website.
Screenshot: affaan-m/ECC (MIT licence)
Sources
- affaan-m/ECC on GitHub (github.com)
- Release v2.2.3 (github.com)
This article was researched and drafted with AI assistance and reviewed against the linked sources by the Nexonic editorial team.
Join the conversation