Add a web-based Codex plugin marketplace and let Codex submit feedback with user approval

Open 💬 2 comments Opened Jun 5, 2026 by 47code

What variant of Codex are you using?

mac IDE

What feature would you like to see?

no-active-thread-019e9628-47dd-7210-92d8-839be056cc1f

Feedback
I have two related requests:

  1. Provide an official web-based entry point for the Codex plugin marketplace
Today, plugins are mainly browsed inside the Codex app. However, the desktop app is not convenient to zoom or browse on a large screen, which makes it harder to review plugin lists, compare capabilities, read installation instructions, understand permissions, and share plugin links.
The plugin ecosystem needs a better public discovery surface, similar to the App Store or Chrome Web Store. A web-based plugin directory could support search, filtering, categories, plugin detail pages, example prompts, permission details, screenshots, changelogs, official vs. third-party labels, installation instructions, and shareable links.
  2. Allow Codex to submit product feedback or issue reports directly, with explicit user approval
Users often describe product feedback clearly inside a Codex conversation, but then still need to find the feedback entry point, copy the text, paste it somewhere else, and submit it manually. That extra step means a lot of valuable feedback dies at the last inch.
It would be helpful if Codex could, after explicit user confirmation, submit the current product suggestion, bug report, or UX issue directly to OpenAI’s feedback system. Ideally, Codex would return a feedback ID or submission status after submitting.

Why this matters
For the plugin ecosystem to grow, users need an easier way to discover, compare, and share plugins. For the product to improve quickly, OpenAI needs a lower-friction path for users to submit real feedback.
When plugin discovery and feedback submission both require extra in-app steps, many users will simply give up. This is especially true because people often assume “someone else must have already reported this,” which can cause obvious issues to receive weaker feedback signals than they deserve.
One-sentence summary
Please add an official web-based Codex plugin marketplace, and allow Codex to submit feedback directly after explicit user approval, so plugin discovery and feedback reporting both become much lower-friction.

Additional information

_No response_

View original on GitHub ↗

2 Comments

watercolorfish · 14 days ago

I would like to add a concrete UX requirement to this proposal.

After preparing a feedback report or support request, Codex should display an editable review card containing the category, message, attachments, and privacy settings. The card should have a real Send button. Clicking Send should count as explicit approval, without requiring the user to separately type “I confirm.”

Replies from either the support bot or a human agent should return directly to the Codex session. If support requests additional information, Codex should prepare a draft response and display it in the same kind of review card before sending.

This is also a cost and reliability issue: working through the browser UI currently requires many model turns, interface inspections, and tokens. A structured first-party API, MCP server, or dedicated tool would be faster, cheaper, and more reliable.

changchangidea-oss · 3 days ago

A concrete OSS experiment related to this discovery gap: SkillRadar (https://github.com/changchangidea-oss/SkillRadar) is a public Codex/Agent Skills discovery + security + routing layer. v0.3.0 continuously discovers real SKILL.md files, parses and safety-grades candidates, classifies them, keeps daily ranking history, and exposes only safety-gated candidates to Codex routing. It also ships a Codex marketplace that is verified in GitHub Actions with: codex plugin marketplace add changchangidea-oss/SkillRadar --ref v0.3.0 && codex plugin add skillradar@skillradar. Sharing as a working example of why a public, shareable plugin discovery surface would be useful.