affaan-m/ECC

Cross-tool capability map

Key architectural decisions: - AGENTS.md at root is the universal cross-tool file (read by Claude Code, Cursor, Codex, and OpenCode; GitHub Copilot uses .github/copilot-instructions.md instead) - DRY adapter pattern lets Cursor reuse Claude Code's hook scripts without duplication - Skills format (SKILL.md with YAML frontmatter) works across Claude Code, Codex, OpenCode, and GitHub Copilot CLI - Codex's narrower native hook set is supplemented by AGENTS.md, optional modelinstructionsfile overrides, and sandbox permissions

ECC provides Cursor IDE support with hooks, rules, agents, skills, commands, and MCP configs adapted for Cursor's project layout.

ECC does not install root AGENTS.md into .cursor/. Cursor treats nested AGENTS.md files as directory context, so copying ECC's repo identity into a host project would pollute that project.

Cursor-native loading behavior can vary by Cursor build. ECC installs agents as .cursor/agents/ecc-.md; if your Cursor build does not expose project agents, those files still work as explicit reference definitions instead of hidden global prompt context.

• Instructions — Native — Native AGENTS.md — Project rules — Plugin instructions — Native instruction file
• Skills — Native installed set — Native plugin set — Build-dependent/project set — Built subset — Native discovery (Copilot CLI) from .github/skills/, .agents/skills/, .claude/skills/
• Agents/delegation — Native agents — Codex multi-agent roles; Claude agent files are not installed as roles — Build-dependent project agents — Plugin agents — Copilot CLI custom agents via .github/agen
• ECC hooks — Native plugin hooks — Native reviewed subset with explicit trust — Cursor hook adapter; install-path differences remain — Plugin events — Not ported; Copilot CLI has its own plugin hook sy
• MCP configuration — Available, explicit activation — Native plugin manifest; legacy sync can merge TOML — Explicit project/user config — Provider/plugin config — Not supplied by ECC
• Parity with Claude Code — Primary reference — Partial — Partial — Partial — Partial
• Hook Events — 15 — sessionStart, beforeShellExecution, afterFileEdit, beforeMCPExecution, beforeSubmitPrompt, and 10 more
• Hook Entrypoints — 15 — Thin Node.js event dispatchers delegating to scripts/hooks/ via shared adapter
• Rules — 34 — 9 common (alwaysApply) + 25 language-specific (TypeScript, Python, Go, Swift, PHP)
• Agents — 48 — .cursor/agents/ecc-.md when installed; prefixed to avoid collisions with user or marketplace agents
• Skills — Shared + Bundled — .cursor/skills/ for translated additions
• Commands — Shared — .cursor/commands/ if installed
• MCP Config — Shared — .cursor/mcp.json if installed
• Cursor sessionStart hook (installed to .cursor/hooks.json on --target cursor) injects ECCAGENTDATAHOME for the whole composer session.

Install with Claude Code

Use the guided setup or native plugin commands. Both install the same ecc@ecc plugin. Choose one and do not stack a full manual Claude install on top.

OSS stays free. This repo is MIT-licensed forever. ECC Pro is the hosted GitHub App for private repos. Sponsors and Pro subscribers fund the work. That's why a single maintainer ships weekly across 7 harnesses.

               

Recommended: universal guided setup

For Claude Code plugin setup, updates, scope changes, and hook-profile changes:

If you are new to command-line tools, use this copy-and-paste path:

This path does not require cloning the repository. If any prerequisite command is not found, install or repair that prerequisite before rerunning ECC setup.

If npm reports a version or cache error, confirm the registry version before retrying:

• Install Node.js 18 or newer, Git, and Claude Code.
• Open PowerShell from the Windows Start menu.
• Confirm that each prerequisite is available:
• Run the guided installer:
• For a typical personal setup, choose Global user, choose Standard hooks, and confirm.
• Start a new Claude Code session and run /plugin list to verify that ecc@ecc is enabled.
• npm / npx — npx ecc-universal@2.2.3 setup
• pnpm — pnpm dlx ecc-universal@2.2.3 setup
• Yarn 2+ — yarn dlx ecc-universal@2.2.3 setup
• Bun — bunx ecc-universal@2.2.3 setup
• Claude Code — Native ecc@ecc plugin with one user, project, or local scope and an ECC hook profile
• Codex — Native Codex marketplace/plugin lifecycle; hook review and trust remain Codex-owned
• Kimi Code — Managed project files under ./.kimi-code; ECC hooks, model/provider settings, and authentication are not configured

npx ecc-universal@2.2.3 setup

Reset / Uninstall ECC

If you installed from the universal package, run these commands from the same project directory used for installation:

From a source checkout, inspect the managed state before reinstalling:

If you are leaving, the uninstall command prints an optional 20-second feedback form. It is a public GitHub issue, never blocks uninstall, and ECC does not upload diagnostics. You can also run ecc feedback at any time to see the problem, feedback, and feature routes.

Plugin users should remove the plugin from Claude Code, then delete only the rule folders they manually copied and no longer want. ECC only removes files recorded in its install-state. It does not claim unrelated files in your harness directories.

• Remove the Claude Code plugin install.
• Run the ECC uninstall command from the project directory that contains the managed install-state.
• Delete any extra rule folders you copied manually and no longer want.
• Reinstall once, using a single path.

npx ecc-universal@2.2.3 list-installed
npx ecc-universal@2.2.3 doctor
npx ecc-universal@2.2.3 repair
npx ecc-universal@2.2.3 uninstall --dry-run
npx ecc-universal@2.2.3 uninstall

Self-Hosted Models and Custom Endpoints

ECC works through each harness's normal configuration, so you can use an official provider, a compatible custom API endpoint or model gateway, or a self-hosted model without changing ECC's workflows.

For Claude Code, ECC does not hardcode Anthropic-hosted transport settings. Minimal gateway example:

If your gateway remaps model names, configure that in Claude Code rather than in ECC. ECC's hooks, skills, commands, and rules are model-provider agnostic once the claude CLI is already working. See Anthropic's LLM gateway documentation and model configuration documentation.

Run or self-host any open-source model behind that gateway using separate compute and serving setup. If you need GPU capacity, Itô is ECC's preferred compute sponsor; any GPU provider works. The sponsorship link is passive: it does not invoke an RFQ, reserve capacity, provision compute, or configure serving. Separately, ecc ito find invokes the explicitly configured canonical Itô CLI and submits a live authenticated RFQ; it does not reserve capacity. Managed inference through Itô is not live yet.

export ANTHROPIC_BASE_URL=https://your-gateway.example.com
export ANTHROPIC_AUTH_TOKEN=your-token
claude