DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to preview, then install ECC into Claude Code and Codex together with ECC

Use the multi-harness wizard to set up two coding agents in one reviewed flow.

Remote script. The guided install runs package code from npm, so review the release source and registry integrity before you confirm.

Who it is forA team lead whose engineers use both Claude Code and Codex and want the same ECC setup in each.

The problemConfiguring two coding agents separately means two sets of choices, and it is easy to end up with mismatched or duplicated installs.

The outcomeClaude Code and Codex are configured in one reviewed run, with a dry-run preview shown before any write.

What you need first

  • Node.js 18 or newer
  • Git on PATH
  • Claude Code 2.1 or newer for plugin setup
  • Access to github.com and npm to fetch the official ECC packages

Steps

  1. Preview the Codex path without writing: npx [email protected] install --guided --harness codex --dry-run.
  2. Run npx [email protected] install --guided and select Claude Code and Codex.
  3. Review each install channel and destination shown, then confirm the single final prompt.
  4. For automation, pass explicit flags: npx [email protected] install --guided --harness claude --harness codex --claude-scope local --claude-hooks standard --profile core --yes. (inferred, check the README)

Prompt for your agent

Using the ECC repo at github.com/affaan-m/ECC, preview a guided install for Claude Code and Codex with `npx [email protected] install --guided` and report the install channel and destination for each harness in <project-path>. Verify that the preview shows no writes before you confirm.

Caveat. The README says Kimi Code hooks, model and provider settings, and authentication are not configured by the guided install, and other adapters are capability-limited.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page