Files
ECC/plugins/ecc/README.md
T
28e53a0bc1 feat(install): add guided multi-harness installer (#2649)
* feat(install): add guided Claude plugin setup

* fix: support Claude command shims on Windows

* feat: support safe Claude plugin scope migration

* fix(install): preserve interactive setup terminal

* fix(install): auto-migrate setup scope changes

* feat(install): add guided multi-harness installer

* fix(install): sync Yarn binary metadata

* fix(install): handle wizard EOF on Node 18

* ci: allow installer matrix tests to finish

* test(install): allow slower PowerShell delegation

* fix(install): harden guided provider reconciliation

* test(install): harden packaged and local compatibility

* chore: prepare guided installer release 2.2.0

* fix(install): report refreshed Codex marketplace state

* fix(install): verify managed content provenance

* test(install): allow empty Yarn smoke fixture

* test(install): invoke Windows package shims safely

* fix(install): close cross-platform release gaps

* fix(install): require trusted GitHub origins

* fix(install): preserve hook profile precedence

* refactor(install): centralize trusted GitHub origins

* ci: retrigger workflow run after merge of main

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-08-06 15:39:49 -04:00

2.0 KiB

plugins/ecc — Legacy Codex Thin-Plugin Artifact

This directory is retained as a legacy compatibility artifact. The current .agents/plugins/marketplace.json points at the self-contained repository root, which Codex 0.146.0 accepts and copies with all referenced runtime content. Do not point the active marketplace back at this thin directory: its parent-relative references are valid in a checkout but escape the isolated plugin cache after installation.

Single source of truth

Per the repo's no-duplication policy, no skill or MCP content is vendored here. .codex-plugin/plugin.json references the canonical root content with parent-relative paths:

Manifest field Resolves to
skills skills/ at the repo root
mcpServers .mcp.json at the repo root
interface.composerIcon / interface.logo assets/ at the repo root

The canonical Codex plugin manifest for the repo-root bundle (used by the official openai/plugins directory shape and other harness tooling) remains at .codex-plugin/plugin.json. Keep name and version in both manifests in sync — tests/plugin-manifest.test.js enforces this and scripts/release.sh bumps both.

Current Codex plugin-mode status

The native marketplace now installs from the repository root. A fresh Codex 0.146.0 cache contains the configure skill, shared skills, MCP configuration, hooks, scripts, and assets, and an authenticated session loads the configure-ecc skill without hook failures.

After install, codex plugin list is not enough to prove the runtime can load the referenced skills and assets. From an ECC checkout, run:

node scripts/codex/check-plugin-cache.js

The check inspects the installed cache under CODEX_HOME (or ~/.codex) and fails if .codex-plugin/plugin.json points at files that were not copied into that cache entry.

The manual sync flow remains available only as a separate legacy compatibility path when copied/merged home configuration is explicitly desired:

npm install && bash scripts/sync-ecc-to-codex.sh