Session management
Track work across multiple sessions and repos so operators can see what changed, what is blocked, and what needs review.
ECC 2.0 Preview · Coming Soon
The next layer is a local-first control plane for agent work.
ECC already covers distribution through the open-source toolkit and protection through AgentShield. The control-plane layer is a planned surface where operators will get visibility across Claude Code, Codex, OpenCode, and Cursor: session management, task orchestration, token optimization, review loops, and shared operating context. This layer is not built yet. The page describes the planned direction.
Planned · Not yet built
Local-first direction above Claude Code, Codex, OpenCode, and Cursor
Operator view, not another isolated config repo
Architecture
How the planned layers fit together.
The website and product should show progression instead of flattening everything into one SKU. Each layer earns the next one.
| Layer | What it does | Why it matters |
|---|---|---|
| Distribution | Skills, commands, hooks, adapters, demos, and install flows through ECC OSS. | Keeps the repo useful and drives top-of-funnel distribution through open adoption. |
| Protection | AgentShield scanning, policy checks, risky-context review, and security baselines. | Makes the harness layer safer for real teams without closing the scanner itself. |
| Control plane | Observability, orchestration, session management, token optimization, and operator coordination. | Turns ECC from a toolkit into the system above the harness layer. |
Preview capabilities
What the app surface is planned to handle.
Task orchestration
Coordinate repeatable workflows above the raw harness: triage, handoffs, queued tasks, and higher-level review loops.
Token optimization
Give teams visibility into context budget usage, waste, and opportunities to make workflows cheaper without reducing quality.
Cross-harness operations
Keep standards and policy coherent even when teams mix Claude Code, Codex, OpenCode, Cursor, and newer harnesses.
Operator review
Expose the right audit points for leads, platform teams, and security partners instead of forcing everyone into raw tool logs.
Team memory
Preserve useful context and conventions across repos and sessions without turning the system into a vendor-locked black box.
Why this page exists now
The gameplan already treats ECC 2.0 as a real medium-term layer. Giving it a visible entry point on the site keeps the architecture honest and gives enterprise conversations a forward-looking destination.
Access path
OSS remains the front door. The GitHub App monetizes the current workflow. The control plane is the next surface for teams that need shared visibility, coordination, and governance above the harness layer.
Start with ECC
Move from OSS discovery to repo-native rollout.
The ECC model stays additive: open-source distribution first, GitHub App automation when repository workflows matter, and enterprise support when the organization needs policy, rollout help, and governance.
74K+ stars
Public repos free
AgentShield protection layer