Platforms

Your tools.
Shared standards.

Bring the skills and workflows you trust to the coding tools you already use.

Native plugins, managed adapters, and a GitHub App. Choose the path for your tool below.

01 / Guided setup

Start with one tool.
Add another when you need it.

ECC 2.2.1 guides setup for Claude Code, Codex, and Kimi Code. Review the destinations before it changes anything.

Run in your terminalnpx ecc-universal@2.2.1 install --guided
A

Claude Code

A native ECC plugin, with your choice of install scope and hook profile.

Claude Code setup
B

Codex

A native marketplace plugin for the app and CLI. Hook review and trust stay with Codex.

Codex setup
C

Kimi Code

Managed project files in .kimi-code. Model settings, authentication, and ECC hooks are left to your existing setup.

Kimi Code setup

Use one install method per harness. If you already use the legacy Codex sync, follow the migration notes before adding the native plugin.

02 / Managed adapters

More ways to work.

Cursor and OpenCode use their own documented install paths. Their setup and hook behavior differ from the guided plugins.

CursorProject-local configuration

Install the minimal profile from a reviewed ECC checkout. Rules and agents live in .cursor/; native agent loading can vary by Cursor version.

./install.sh --profile minimal --target cursorRead Cursor instructions
OpenCodeBuilt plugin payload

Use the documented checkout workflow to build the OpenCode plugin before installation. The full profile includes an explicit hook choice; copying the raw config folder alone is not the complete install.

Read OpenCode instructions
Explore the full platform support guide
GitHub
03 / At the repository

Keep review close to the code.

Add the ECC GitHub App for repository workflows, or AgentShield for configuration scanning in your development and CI flow.

Product names and marks belong to their respective owners. The OpenAI mark identifies the company behind Codex. Compatibility does not imply endorsement.