Affaan MustafaandGitHub
0348d7b6d7
pi/core and the bundled blueprint skill now refer to the project as ECC only; the generated README no longer expands the name. Profile contents, package name and paths are unchanged (123 skills, 24 commands). The release workflows poll npm for up to five minutes after publish before verifying the artifact. In 2.2.2 the check gave up after about 30 seconds while npm was still processing, failing the run before latest was promoted and the GitHub Release was created. Version metadata synced to 2.2.3 with CHANGELOG, translated release headings and release notes; skill-triggers registryDigest updated for the blueprint text.
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