Claude Code
The deepest ECC surface today: skills, hooks, commands, and the most mature workflow customization.
Platforms
ECC is built for teams that refuse to bet everything on one harness forever.
The platform page makes cross-harness support visible. ECC should preserve standards, workflows, and security posture even when the front-end tool changes underneath the team.
Claude Code deepest workflow depth
Codex app + CLI parity
OpenCode plugin and adapter path
Cursor workflow support today
Codex
Strong validation for the composable-unit model: shared skills, reusable commands, and parity across app and CLI workflows.
OpenCode
An important open harness target and a good proving ground for adapter architecture, plugin support, and portable workflows.
Cursor
Important because engineering teams already use it heavily, so portability, policy, and shared conventions matter immediately.
Parity roadmap
- Selective install profiles that work across harnesses
- Shared policy and security scanning concepts
- Common skill and workflow packaging
- Operator visibility above individual tool sessions
Why this matters commercially
If ECC only behaved like a single-tool fan repo, the ceiling would stay low. If it stays useful above the harness layer, it remains relevant as the tool landscape shifts.
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