ECC v2.2.0

v2.2.0

ECC 2.2.0: Guided Setup, Antigravity 2.0, and the Nasiko CLI Bridge

Added 5
  • Add guided installer for Claude Code, Codex, and Kimi harnesses
  • Add native Antigravity 2.0 support with installation to .agents/{rules,workflows,skills,agents}
  • Add experimental, opt-in Nasiko CLI lifecycle bridge for inspecting, installing, and removing Nasiko v0.1.0
  • Add 68 agents, 286 skills, and 94 command shims in the shipped distribution
  • Add Pi, Itô, agent evaluation, multi-model council, dev-team, living docs, secure terminal, TasteForge, and skill-comply workflows
Changed 4
  • Improve installer to check every selected harness before writing files and apply setup as one operation
  • Improve release pipeline to require the exact npm archive to pass lifecycle tests on Linux, macOS, and Windows before latest tag moves
  • Improve uninstall reliability by maintaining a complete ownership ledger for selective installs
  • Improve migrations by preserving edited or untracked files during cleanup for OpenCode and Codex
Fixed 1
  • Fix legacy Antigravity ownership migration during installation
Security 1
  • Add SHA-256 verification for Nasiko CLI downloads

From ECC

ECC 2.2 is here, led by one guided installer for Claude Code, Codex, and Kimi. It also adds native Antigravity 2.0 support and an experimental, opt-in Nasiko CLI lifecycle bridge.

The release pipeline is stricter too: the exact npm archive must pass lifecycle tests on Linux, macOS, and Windows before latest moves.

One guided path into ECC

ECC 2.2 terminal welcome after a successful install

Start the guided installer with:

npx --yes ecc-universal@2.2.0 install --guided

The installer checks every selected harness before writing files, then applies the setup as one operation. Provider-owned model and authentication settings stay under the provider's control. The terminal welcome appears only after a successful interactive install.

Nasiko: experimental, opt-in, and explicit

Nasiko's open-source agent dashboard, shown as product context for the ECC CLI lifecycle bridge

ECC 2.2 can inspect, install, and remove one pinned Nasiko v0.1.0 CLI build:

npm install -g ecc-universal@2.2.0
ecc nasiko status --json
ecc nasiko install --version v0.1.0 --dry-run --json
ecc nasiko install --version v0.1.0 --yes --json

Downloads are content-addressed and SHA-256 verified, status is read-only, and uninstall protects modified or unqualified binaries. The dashboard above is Nasiko's own product. ECC does not connect agents, start a server, enable telemetry, share data, or operate that control plane. The bridge remains experimental and opt-in.

Learn more in the Nasiko repository.

More reliable across every harness
  • Native Antigravity 2.0: ECC installs to .agents/{rules,workflows,skills,agents} and safely migrates legacy ownership.
  • Reliable uninstall: repeated selective installs keep a complete ownership ledger, so unchanged ECC-managed files can be removed cleanly.
  • Safer migrations: OpenCode uses ~/.config/opencode, while OpenCode and Codex preserve edited or untracked files during cleanup.
  • More workflows: Pi, Itô, agent evaluation, multi-model council, dev-team, living docs, secure terminal, TasteForge, and skill-comply all expand the shipped distribution.

ECC 2.2 ships 68 agents, 286 skills, and 94 command shims, plus the rules, hooks, memory, continuous-learning, and installation surfaces around them.

Release assurance

The tagged commit must match origin/main. One npm archive is packed, hashed, and tested on all three operating systems, then published under a staging tag. Registry integrity must match before latest moves. The prior 2.1.0 package remains the immediate rollback target.

Install or upgrade

For the native Claude Code plugin:

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

Existing Claude installs can run /plugin update ecc.

Thank you

A special thank you to returning contributors @gaurav0107, @Seekers2001, and @t0kubetsu for substantial work on learning workflows, collaborative skills, and shared testing.

Among our first-time contributors, @renan-tiberio brought Pi support, @romanclaudersoai1 repaired /evolve, and @djpjronline-netizen hardened hook parsing.

Eighteen people made their first ECC contribution in 2.2. Thank you to everyone who tested the installer, reported issues, and helped harden the release across harnesses and operating systems.

New contributors

Join us in the ECC Discord.

Full changelog: https://github.com/affaan-m/ECC/compare/v2.1.0...v2.2.0

View original

Upgraded? How did it go?

Discussion