Repository navigation
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.707.6957.0
What subscription do you have?
Not included
What platform is your computer?
Windows 11, Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
When the remote Superpowers plugin is mentioned in the Codex Desktop composer, its icon renders as a broken image. The same plugin icon renders normally after the message appears in conversation history.
The plugin itself remains functional; this appears to be isolated to composer icon rendering for the remote plugin surface.
Plugin details:
- Plugin:
superpowers@openai-curated-remote - Plugin release:
6.1.1 - Plugin ID:
plugins~Plugin_60aea7460bd4819199fd97a9553a5e12
What steps can reproduce the bug?
- Open Codex Desktop on Windows.
- Start a new task or focus the message composer.
- Select/mention
Superpowersfromopenai-curated-remote. - Observe that the icon immediately before “Superpowers” is a broken-image placeholder.
- Send the message.
- Observe that the icon shown for the plugin mention in conversation history renders normally.
The behavior persists after restarting Codex and while using the latest available desktop client.
What is the expected behavior?
The Superpowers icon should render consistently in both the composer and conversation history.
Additional information
Local investigation found:
- The remote plugin catalog contains both
composer_icon_urlandlogo_url. - A direct request to each catalog URL returns HTTP 403.
- The response body for the composer icon URL is:
{"detail":"File stream access denied."} - The local 6.1.1 plugin bundle contains a valid
assets/superpowers-small.svg, so the packaged icon asset is present. codex doctor --allreports17 ok · 1 idle · 0 warn · 0 fail.- Current desktop logs do not report a missing local Superpowers asset.
This suggests the composer may be attempting to render a remote icon URL that is not accessible in that rendering path, while history uses a cached, inlined, or otherwise resolved icon.
A screenshot demonstrating the composer/history difference is available if needed.
Activity
ilovex1314 commentedon Jul 17, 2026
Confirming the same issue on macOS, and it also affects Remotion.
Environment
26.715.21425(build5488)26.5.2(25F84)6.1.11.0.5Observed behavior
superpowers@openai-curated-remoteshows a broken-image placeholder in the composer.remotion@openai-curated-remoteshows the same behavior.Diagnostics
For both Superpowers and Remotion, the remote catalog's
composer_icon_urlpoints to:A direct request returns:
As a control, plugin icons hosted at
https://files.openai.com/content...returnHTTP 200with valid image bytes.The packaged local assets are present and valid:
assets/superpowers-small.svgI also verified that
chatgpt.comandfiles.openai.comuse the same network policy and outbound route; there is no domain split or DIRECT/proxy mismatch that would explain the different responses.Temporarily replacing the cached remote
composer_icon_urlwith an inline image and reloading the app-server makes the composer icon render correctly. However, restarting Codex refreshes the remote catalog and restores the inaccessible Estuary URL, so the issue returns.This appears to be a remote catalog asset authorization/publishing problem, combined with the composer not falling back to the valid icon in the locally cached plugin bundle. A robust fix could either republish these assets with readable URLs or fall back to the packaged local
composerIconwhen the remote image cannot load.