ECC v1.10.0 is live — 140K stars, 156 skills, and ECC 2.0 alpha in-tree

[affaan-m]

ECC v1.10.0 is live

ECC just crossed 140K stars, and the public release surface had drifted too far from the actual repo.

So v1.10.0 is a hard sync release:

• 38 agents
• 156 skills
• 72 commands
• plugin/install metadata corrected
• top-line docs and release surfaces brought back in line

This release also folds in the operator/media lane that has been growing around the core harness system:

• brand-voice
• social-graph-ranker
• connections-optimizer
• customer-billing-ops
• google-workspace-ops
• project-flow-ops
• workspace-surface-audit
• manim-video
• remotion-video-creation

And on the 2.0 side:

ECC 2.0 is now real as an alpha control-plane surface in-tree under ecc2/.

It builds today and exposes:

• dashboard
• start
• sessions
• status
• stop
• resume
• daemon

That does not mean the full ECC 2.0 roadmap is done.

It means the control-plane alpha is here, usable, and moving out of the “just a vision” category.

The shortest honest framing right now:

• ECC 1.x is the battle-tested harness/workflow layer shipping broadly today
• ECC 2.0 is the alpha control-plane growing on top of it

If you have been waiting for:

• cleaner install surfaces
• stronger cross-harness parity
• operator workflows instead of just coding primitives
• a real control-plane direction instead of scattered notes

this is the release that makes the repo feel coherent again.

[aouatef2001]

to get 1 star in your project gihub its like flying to sky hhhhhh

[lexamarketolog]

Wow! That's awesome! Thank you!

[aouatef2001]

It's okay

[Adam2023Adsteera]

do you have a Video tutorial how to use ECC v1.10.0 , i am getting confuse as i am a newbie

[FrankEnglish]

Hi, since I installed the package for Claude Code, I’ve noticed a much faster token consumption. Is it possible that this system is the cause?

[affaan-m]

Quick release/install clarification because the public surfaces drifted:

• GitHub release/tag v1.10.0 exists.
• npm ecc-universal is still at 1.9.0 right now.
• the everything-claude-code package name is not currently live on npm.

So the repo/release metadata moved ahead of the npm publish step. I am treating that as release plumbing drift, not pretending the 1.10.0 npm package shipped when it did not.

Separately, the old ecc@ecc plugin install string is stale. The canonical marketplace/plugin identifier is everything-claude-code@everything-claude-code, and the reason for standardizing on the full name is to keep the repo/docs/install surface aligned with the Anthropic marketplace/plugin model instead of a shorthand that only made sense historically.

The urgent install/name/GateGuard fixes are consolidated in #1439:
#1439

That is the current branch to watch for the install breakage people are reporting.

[affaan-m]

Follow-up clarification because the same two questions keep coming up in this thread:

1. Release/publish state:

• GitHub release/tag v1.10.0 exists.
• npm ecc-universal is still 1.9.0 right now.
• the everything-claude-code package name is not currently live on npm.

So if you installed from npm, you did not receive a 1.10.0 npm package yet. The repo/release metadata moved ahead of npm publish. I am treating that as release plumbing drift and fixing the release/update surfaces accordingly instead of pretending npm already shipped.

2. Why the plugin/install name changed:

• older shorthand like ecc@ecc is historical drift
• Anthropic marketplace/plugin installs are keyed by a canonical plugin identifier
• standardizing on everything-claude-code@everything-claude-code keeps the marketplace listing, install command, /plugin list, and docs aligned to one public name

That rename was not done for aesthetics. It was done so the plugin can be listed and resolved consistently through the Anthropic marketplace/plugin model instead of maintaining a repo-local nickname that breaks discovery and support.

On token usage: ECC itself is not a hidden billing service, but a broader install surface can increase context/tool activity depending on what you install and how you run it. If you want the leanest path, use the selective/core install rather than copying the whole repo surface blindly.

The urgent Windows install/name/GateGuard fixes are consolidated here: #1439

[affaan-m]

Quick clarification on the release state, since this confused people:

• GitHub release v1.10.0 exists.
• npm ecc-universal did not get a 1.10.0 publish.
• the old everything-claude-code npm package is unpublished.

Root cause: the release workflows were creating GitHub releases but were not publishing to npm. I opened #1446 to fix that and to make the naming/migration story explicit in the docs.

Current canonical names are:

• GitHub repo: affaan-m/everything-claude-code
• Claude marketplace/plugin identifier: everything-claude-code@everything-claude-code
• npm package: ecc-universal

The marketplace/plugin identifier changed so the Anthropic marketplace listing, /plugin install, /plugin list, and repo docs all use one canonical public install surface instead of maintaining two names for the same plugin.

Urgent install/name/GateGuard regressions are already fixed on main via #1439. The remaining plugin-installed hook bootstrap fix is in #1445 and the npm/release-name fix is in #1446.

[affaan-m]

Release status update: the workflow fixes are now on main, and I manually reran the v1.10.0 release workflow to catch npm up to the existing GitHub release. The rerun reached npm publish and then failed with ENEEDAUTH because NODE_AUTH_TOKEN was empty. So the remaining blocker is operational, not code: the repository currently does not have a usable NPM_TOKEN Actions secret configured. Until that secret is added and the release workflow is rerun, GitHub will show v1.10.0 while npm ecc-universal remains at 1.9.0.

[affaan-m]

Operational update: the npm catch-up is complete now. ecc-universal@1.10.0 is live on npm and the latest dist-tag now points to 1.10.0. The earlier gap was a release-workflow issue: GitHub v1.10.0 existed, but the original publish path had not actually completed npm publication. That workflow has been fixed on main, the missing token was added, and the release was rerun successfully.

[affaan-m]

Status update:\n\n- npm ecc-universal@1.10.0 is now live and tagged as latest\n- the release workflow/auth gap is fixed on main\n- the Bash hook fork-storm fix is also merged on main via #1449\n\nThe remaining user-visible install/runtime issue is the Claude Code 2.1.x hook schema break tracked in #1454. I reproduced it, confirmed the shipped hooks/hooks.json shape was wrong for current Claude Code validation, and opened the fix here: #1462\n\nI am treating #1462 as the last urgent patch in this stabilization pass. Once that lands, I will post a single consolidated follow-up so people have one current status point instead of piecing it together from multiple threads.

[affaan-m]

Consolidated stabilization update:\n\nThe major install/runtime breakages from the 1.10.0 rollout are now resolved on main:\n- ecc-universal@1.10.0 is live on npm\n- the release workflow/auth gap is fixed\n- the Bash hook fork-storm fix is on main\n- the Claude Code 2.1.x hooks.json command-shape fix is on main via #1462\n\nI am intentionally not over-claiming beyond that. We are still watching for edge cases across OS variations, install paths, and different harness environments.\n\nIf you were blocked, the practical next step is to update/reinstall so you pull the corrected package and hook files. If anything is still broken after that, please open a fresh issue with:\n- OS and shell\n- Claude Code version\n- install method used\n- exact stderr/output\n- whether the problem is marketplace install, self-hosted marketplace, npm install, or local repo sync\n\nThat gives us a cleaner signal than continuing to pile unlike symptoms into older threads.

[affaan-m]

Release follow-up status:\n\nThe last active 1.10.1 release gate is now cleared. #1546 is merged on main, which means the continuous-learning-v2 plugin quick start is no longer telling plugin users to paste stale manual hook paths into settings.json.\n\nThat puts the current stabilization set on trunk:\n- Cursor native project install repair via #1543\n- Claude Code v2.1.116 argv-dup mitigation via #1524\n- claude-desktop support in continuous-learning-v2 via #1522\n- Windows observe-path hardening via #1511\n- plugin-vs-manual continuous-learning doc correction via #1546\n\nAt this point the remaining work before 1.10.1 is release management and any conscious decision to include or exclude additional non-gating items, not waiting on a still-broken install path.