Codex Desktop: Stripe plugin page is visible in Plugins, but Stripe is not actually installable

What version of the Codex App are you using (From “About Codex” dialog)?

Unknown at filing time.

What subscription do you have?

Unknown at filing time.

What platform is your computer?

macOS (desktop app screenshot from a Mac environment).

What issue are you seeing?

In Codex Desktop, the Plugins catalog shows a dedicated Stripe page with an Add to Codex button and included skills such as:

• Stripe Best Practices
• Upgrade Stripe

However, Stripe does not appear to be actually available as an installable plugin in the current Codex environment.

Observed behavior from the affected environment:

• The user can navigate to Plugins -> Stripe.
• The UI presents Stripe as if it can be added to Codex.
• In the active Codex environment, Stripe-related skills are discoverable, but Stripe is not exposed as an installable plugin in the installable plugin list.
• This makes the product surface ambiguous: Stripe looks available in the catalog, but is not actually addable for this account/build/session.

This appears to be either:

1. a catalog/UI mismatch,
2. account/rollout gating that is not explained in-product, or
3. a plugin install path failure specific to Stripe.

What steps can reproduce the bug?

1. Open Codex Desktop on macOS.
2. Open Plugins.
3. Navigate to Stripe.
4. Observe that the Stripe plugin page exists and shows an Add to Codex affordance.
5. Compare against the actually installable plugins available in the same Codex environment.
6. Observe that Stripe is not exposed as an installable plugin, despite the catalog page implying that it is available.

What is the expected behavior?

If Stripe is not available for the current user/account/platform/rollout, the UI should say so clearly instead of presenting it as addable.

If Stripe is intended to be installable, then the Add to Codex path should work and Stripe should appear in the actual installable plugin set for the environment.

Additional information

This looks similar in shape to other plugin availability/discoverability issues, for example Figma being visible but unavailable (#19158), but this report is specifically about Stripe.

Useful product clarification would be one of:

• hide Stripe from the catalog when it is not installable,
• show a clear unavailable/gated state with the reason, or
• make the add/install flow succeed when the page is shown as available.

I am filing this based on a real user report plus the current Codex environment evidence that Stripe-related skills are bundled while Stripe is not present in the installable plugin list.