ECC 2.2.0: Guided Setup, Antigravity 2.0, and the Nasiko CLI Bridge #2887
Replies: 1 comment
|
Discord delivery: complete (message 1542588146389360712). |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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
latestmoves.One guided path into ECC
Start the guided installer with:
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
ECC 2.2 can inspect, install, and remove one pinned Nasiko
v0.1.0CLI build: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
.agents/{rules,workflows,skills,agents}and safely migrates legacy ownership.ledger, so unchanged ECC-managed files can be removed cleanly.
~/.config/opencode, while OpenCode andCodex preserve edited or untracked files during cleanup.
living docs, secure terminal, TasteForge, and
skill-complyall expand theshipped 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
latestmoves. The prior 2.1.0 packageremains the immediate rollback target.
Install or upgrade
For the native Claude Code plugin:
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: v2.1.0...v2.2.0
All reactions