Codex Desktop Stripe plugin install fails due to remote bundle plugin.json name mismatch

Open 💬 0 comments Opened Jul 9, 2026 by bizwizcb

What issue are you seeing?

Codex Desktop fails to install the Stripe remote plugin. The failure occurs after the remote bundle download path starts; the app server rejects the bundle because the internal plugin.json.name does not match the marketplace plugin slug.

Environment

  • App: Codex Desktop
  • Client version observed in logs: 26.623.141536
  • OS: Windows 11 Professional x64
  • Marketplace: openai-curated-remote
  • Plugin: Stripe
  • Remote plugin ID: plugin_connector_690ab09fa43c8191bca40280e4563238

Exact error from local Codex logs

remote plugin install failed
remote_plugin_id=plugin_connector_690ab09fa43c8191bca40280e4563238
marketplace_name=openai-curated-remote
error_type=remote_bundle_store
error=plugin.json name `app-6983c208e5f8819196b7511519f97993` does not match marketplace plugin name `stripe`

The same failure appeared twice around July 8, 2026, 3:55 PM local time.

Expected behavior

The Stripe plugin should install successfully and create an active remote cache entry similar to:

C:\Users\<user>\.codex\plugins\cache\openai-curated-remote\stripe

The installed bundle should expose its Stripe skills/tools in fresh Codex Desktop threads.

Actual behavior

No active remote Stripe plugin cache entry is created under openai-curated-remote\stripe. Install fails because the bundle's plugin.json.name is app-6983c208e5f8819196b7511519f97993 while the marketplace name is stripe.

A legacy local cached Stripe payload exists under openai-curated\stripe\9c1190e4 and has a correct local manifest name of stripe, but that does not repair the current remote install path.

Suggested corrective action

  1. Republish the Stripe remote plugin bundle with plugin.json.name set to exactly stripe.
  2. Confirm .app.json still references the intended Stripe connector ID.
  3. Add or enforce a publishing-time validation check that rejects any remote plugin bundle when plugin.json.name differs from the marketplace plugin slug.
  4. Verify the fix through Codex Desktop's plugin install UI on Windows, not only through backend/tool discovery.

Notes

The Stripe connector tools can still be discoverable in some Codex contexts, but the Desktop plugin install path itself is failing due to remote bundle manifest validation.

View original on GitHub ↗