Summary

On Windows with Codex CLI 0.130.0, a local plugin placed via the documented personal marketplace flow is still not discovered by a fresh Codex runtime.

This does not look specific to one plugin repo. We reproduced it with a third-party plugin (ECC) and also found several related Codex issues around marketplace registration, local plugin discovery, and plugin/runtime exposure.

The important point is that this was not only tested through codex plugin marketplace add .... We also tried the documented personal marketplace layout manually and Codex still did not recognize the plugin.

Environment

• OS: Windows
• Codex CLI: 0.130.0
• Host usage: Codex desktop + local CLI/runtime (codex exec)

What we tested

Path A: plugin repo's own marketplace config

The plugin repo includes:

• .agents/plugins/marketplace.json
• .codex-plugin/plugin.json
• skills/
• .mcp.json

In this repo's shipped marketplace file, the plugin entry uses:

"source": {
  "source": "local",
  "path": "./"
}

That already looks close to #17066, so we did not stop there.

Path B: documented personal marketplace flow

We then bypassed the repo's own marketplace config and manually installed it using the personal marketplace layout described by Codex's plugin tooling/docs:

• ~/.agents/plugins/marketplace.json
• ~/plugins/ecc/
• ~/plugins/ecc/.codex-plugin/plugin.json
• ~/plugins/ecc/skills/
• ~/plugins/ecc/.mcp.json

Personal marketplace entry used:

{
  "name": "personal",
  "interface": {
    "displayName": "Personal"
  },
  "plugins": [
    {
      "name": "ecc",
      "source": {
        "source": "local",
        "path": "./plugins/ecc"
      },
      "policy": {
        "installation": "AVAILABLE",
        "authentication": "ON_INSTALL"
      },
      "category": "Productivity"
    }
  ]
}

Expected behavior

A plugin installed via the documented personal marketplace layout should at least become discoverable to a fresh Codex runtime.

Even if not all capabilities are active yet, I would expect one of the following:

• the plugin appears in the visible plugin set
• the plugin produces a corresponding local plugin cache entry
• there is a clear runtime error that the plugin was found but rejected

Actual behavior

After starting a fresh codex exec runtime:

• the plugin did not appear in the visible plugin set
• ~/.codex/plugins/cache/ did not gain a corresponding personal plugin cache entry
• runtime still only exposed the pre-existing plugins already available on the machine

In our case, the fresh runtime still reported only the existing built-in/curated plugins, not ECC.

Additional signal that may matter

On this machine, codex plugin --help only shows:

• marketplace

It does not expose subcommands like:

• plugin add
• plugin list

That seems inconsistent with the local plugin installation/update flow described by the built-in plugin tooling/docs, and may point to either:

• version skew between CLI/runtime and plugin docs/tooling
• platform/channel differences in plugin support
• incomplete local plugin support in this release

Why I think this is not an isolated repo mistake

This looks related to a broader local plugin / marketplace discovery instability rather than only this plugin repo:

• #17066 local marketplace path/root issue
• #22078 local plugin/skills not exposed
• #23902 marketplace written but not really consumed
• #24736 plugins not appearing / No plugins found
• #21791 plugin/runtime visibility mismatch

Main ask

Can you clarify whether local/personal marketplace plugins are expected to work on Windows in 0.130.0, and if so, what the canonical supported discovery path is for:

• ~/.agents/plugins/marketplace.json
• ~/plugins/<plugin-name>/
• fresh runtime pickup in codex exec

Right now it is hard to tell whether this is:

• unsupported/partial support in this version
• a Windows-specific discovery bug
• stale documentation/tooling around personal marketplaces
• or a broader local plugin discovery regression