Skip to content

Codex Desktop: remote plugin composer icon renders as broken image while history icon works #32677

Open

Description

@wangzhihaolighter

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?

  1. Open Codex Desktop on Windows.
  2. Start a new task or focus the message composer.
  3. Select/mention Superpowers from openai-curated-remote.
  4. Observe that the icon immediately before “Superpowers” is a broken-image placeholder.
  5. Send the message.
  6. 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_url and logo_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 --all reports 17 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

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    skillsIssues related to skills
    windows-osIssues related to Codex on Windows systems
    on Jul 13, 2026
  2. ilovex1314 commented on Jul 17, 2026

    @ilovex1314

    Confirming the same issue on macOS, and it also affects Remotion.

    Environment

    • Codex Desktop: 26.715.21425 (build 5488)
    • macOS: 26.5.2 (25F84)
    • Architecture: Apple Silicon / arm64
    • Superpowers: 6.1.1
    • Remotion: 1.0.5

    Observed behavior

    • superpowers@openai-curated-remote shows a broken-image placeholder in the composer.
    • remotion@openai-curated-remote shows the same behavior.
    • After sending the message, the plugin mention/icon renders normally in conversation history.
    • Both plugins remain functional.
    • Restarting Codex consistently reproduces the broken composer icon.

    Diagnostics

    For both Superpowers and Remotion, the remote catalog's composer_icon_url points to:

    https://chatgpt.com/backend-api/estuary/content?...&cid=8&...
    

    A direct request returns:

    HTTP 403
    {"detail":"File stream access denied."}
    

    As a control, plugin icons hosted at https://files.openai.com/content... return HTTP 200 with valid image bytes.

    The packaged local assets are present and valid:

    • Superpowers: assets/superpowers-small.svg
    • Remotion: packaged PNG icon

    I also verified that chatgpt.com and files.openai.com use 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_url with 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 composerIcon when the remote image cannot load.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingskillsIssues related to skillswindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions