Install in one command
Everything auto-wires — agents, RTK compression, Terse mode, codebase graph, MCP server. Zero configuration required.
npm i -g kodelyth-eccNode.js 18 or newer. This puts two identical binaries on your PATH — kodelyth-ecc and the shorter kodelythecc. Use whichever you prefer; every example here uses the short one.
kodelythecc --target claude-code --codebase-graphCopies 70 agents, 196 skills, 103 commands, 44+ hooks and 15 rules into ~/.claude/, installs RTK, drops in Terse mode, and wires the codebase graph. Then restart Claude Code — it reads that directory at startup, so a running session will not see any of it.
Targets come in two kinds, and the difference decides where you stand when you run the command.
Installs into your home directory
Run these from anywhere. They apply to every project on the machine.
kodelythecc --target claude-home
kodelythecc --target codex-home
kodelythecc --target windsurf-home
kodelythecc --target gemini-homeInstalls into the current project
cd into the project first. These write into the folder you are standing in, so running one from your home directory scatters ECC files there instead.
kodelythecc --target cursor-project
kodelythecc --target antigravitykodelythecc --target windsurf-projectkodelythecc --target gemini-project
kodelythecc --target opencode
kodelythecc --target cline
kodelythecc --target roocode
kodelythecc --target aider
kodelythecc --target kimiThe same commands work. kodelythecc detects Windows and runs the PowerShell installer for you — there is nothing separate to download, and you do not need to change your execution policy.
Node.js 18+ and either PowerShell 7 (pwsh) or the Windows PowerShell 5.1 that ships with the OS. The installer tries pwsh first and falls back on its own.
Everything installs automatically, same as macOS and Linux: all 70 agents, 196 skills, 103 commands, 15 rules, every hook registered into your settings, the MCP server, Terse mode, RTK, and the codebase graph.
RTK and the codebase graph are native binaries. ECC downloads the published Windows builds and puts them in %LOCALAPPDATA%\Kodelyth\bin, which is not on PATH by default — so it prints the one command that fixes it:
setx PATH "%PATH%;%LOCALAPPDATA%\Kodelyth\bin"Run it once, reopen your terminal, done. ECC does not edit your PATH for you.
kodelythecc doctorOne command that checks every subsystem and prints a line per component — binaries on PATH, what landed in your install target, RTK, Terse, the codebase graph and MCP. If something is wrong it says which piece and why, which beats running five status commands and guessing.
Prefer to check each piece individually?
kodelythecc --version
kodelythecc rtk status
kodelythecc terse status
kodelythecc codebase status
kodelythecc mcp-listType kodelythecc on its own and an arrow-key menu opens — update check, dashboard, IDE picker, background daemon, and full uninstall. You never have to remember a flag.
ECC leaves a clean footprint. Removal is interactive and dry-run friendly: it takes back every file it shipped, unwires RTK and the codebase graph from your IDE configs, and deletes the ~/.kodelythecc/ memory stores. Nothing of yours is touched.
# See exactly what would go, change nothing
kodelythecc uninstall --dry-run
# Do it
kodelythecc uninstall --yes
# Remove the binary itself
npm uninstall -g kodelyth-eccSend us the output of kodelythecc doctor and the exact command you ran — that is almost always enough to spot it straight away.