Guided preview
Inspect a planned Codex installation without applying the configuration changes.
ECC
ECC packages Skills, hooks, and configuration tools for coding agents. Its CLI can preview a Codex installation and show what it will configure before you approve a write.
Preview ECC changes for Codex
Plan the package version, host and write scope before an agent touches configuration.
Give the workspace path, current host version and allowed setup scope.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatYour request for Floatboat
Preview and copy the request. It is not sent automatically from this page.
Reference: ECC https://github.com/affaan-m/ECC Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: Read the official ECC install instructions. Check Node and Codex, then show me the guided Codex dry-run command. After approval, run only the preview and report its destination and proposed writes. Expected deliverable: A dry-run report and a reviewable list of proposed writes.
About ECC
ECC groups engineering workflows with an installer and diagnostics for multiple coding agents. Its guided setup can target Claude Code, Codex, and Kimi Code, with different setup behavior for each host.
For Codex, use the documented guided dry run to inspect the installation channel and target before writing. The real install uses Codex’s native plugin flow. Hook review and trust decisions remain in Codex.
Record the package version, selected host and expected scope in the project handoff. Run diagnostics after setup where the host supports them. Keep additional adapters, authentication, and provider configuration separate when evaluating the result.
What ECC Configures
A dry run answers where the package would go. Use the selected host’s diagnostics and plugin controls to check what was actually enabled.
Host-specific setup
Use each documented install channel and review hooks in the host that will execute them.
Diagnosis
Check supported targets for setup issues and record the confirmed state before sharing instructions.
ECC Use Cases for Coding-Agent Setup
Use ECC on a disposable or approved workspace first. Compare configuration evidence with a small task so installation and workflow behavior can be reviewed independently.
Preview a Codex setup
Record the current plugin state, run the documented dry run, and capture its destination and proposed actions. Ask the workspace owner to approve those changes before installation.
Scope a Claude Code trial
Choose a local, project or user installation scope before you run the installer. Compare the requested hooks with the scope you intend, then check the plugin list after the approved change.
Review a team handoff
Write a short setup note listing the installed package version, host and profiles. Ask a teammate to reproduce the preview on a clean workspace and compare the proposed paths.
Investigate a setup mismatch
When a Skill is missing, compare the selected host and install scope with the upstream instructions. Collect the diagnostics available for that target before making a second configuration change.
ECC Setup Requirements
The guided package requires Node.js and a supported host. Check the host and package version and reserve a confirmation step before modifying configuration.
Package runtime
The documented universal installer needs Node.js 18 or later.
Host setup
Make the chosen host available and check the requirements for its installation channel.
Approved scope
Review destination, hooks and plugin trust before applying the planned setup.
Related Software Projects
Compare the workflows, operating requirements, and source licenses of these projects.
ECC FAQ
Which hosts have guided setup?
The documented guided installer covers Claude Code, Codex and Kimi Code. Other adapters use separate documented commands.
Can I see changes before installing?
For Codex the README documents an install command with --dry-run. Review the proposed destination and actions before approving writes.
Does ECC grant trust to Codex hooks?
Codex retains control of hook review and trust in its native plugin installation flow.
What does the Claude Code setup require?
In addition to Node.js, the official Claude Code plugin setup requires Git and a supported Claude Code executable on PATH.
Does setup configure a model provider?
Check the selected host documentation. The managed Kimi path, for example, does not configure model settings or authentication.
How do I check a successful install?
Inspect the host’s plugin or Skill state, then try a bounded task that exercises the capability you enabled.