Clarify contribution path for Codex plugin marketplace localization

Summary

I would like to help localize the Codex App plugin marketplace content into Traditional Chinese (Taiwan).

In the Codex desktop app, the plugin marketplace UI is partially localized, but many marketplace-facing plugin strings are still shown in English. Examples visible in the attached screenshot include:

• Computer Use - Control Mac apps from Codex
• Chrome - Control Chrome with Codex
• Spreadsheets - Create and edit spreadsheet files
• Presentations - Create and edit presentations
• GitHub - Triage PRs, issues, CI, and publish flows
• Slack - Read and manage Slack
• Google Drive - Work across Drive, Docs, Sheets, and...
• Outlook Email - Triage Outlook inboxes and draft replies
• Vercel - Build and deploy web apps and agents

What I found

I checked openai/codex and found that the current plugin manifest parser/spec appears to support marketplace-facing fields such as:

• interface.displayName
• interface.shortDescription
• interface.longDescription
• interface.defaultPrompt

However, I did not find a documented localization mechanism for plugin metadata, such as translations, locale-specific interface values, or i18n files.

Relevant files I looked at:

• codex-rs/core-plugins/src/manifest.rs
• codex-rs/core-plugins/src/marketplace.rs
• codex-rs/skills/src/assets/samples/plugin-creator/references/plugin-json-spec.md

I also noticed that some plugin marketplace strings shown in the Codex App appear to come from openai/plugins manifests, for example plugins/github/.codex-plugin/plugin.json.

There is also an open PR in openai/plugins that seems related:

• openai/plugins#50 - Localization for plugins - [Do not merge]

That PR appears to experiment with a translations field, but it is marked [Do not merge], so I am not sure whether this is the intended public contribution path.

Questions

Could you please clarify:

1. Is localization of Codex plugin marketplace metadata currently supported or planned?
2. If supported, where should translations be contributed: openai/codex, openai/plugins, or another repository/source?
3. What schema should be used for localized plugin metadata?

• For example, should translations live under interface.translations, top-level translations, or another structure?

1. What locale key should be used for Traditional Chinese (Taiwan)?

• For example: zh-TW, zh_tw, or another canonical format?

1. Are community pull requests for plugin marketplace localization welcome?
2. How should built-in plugins that do not appear in openai/plugins be localized?

• For example: Computer Use, Chrome, Spreadsheets, and Presentations.

I am happy to help provide Traditional Chinese (Taiwan) translations for these plugin marketplace strings if there is an accepted contribution path.

Screenshot

Screenshot of the current Codex App plugin marketplace: