openai / openai/codex

Codex Cloud image outputs invisible in both web and macOS desktop, including minimal PNG test

Open
#45,731 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug codex-web tool-calls
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Problem

Image outputs from a Codex Cloud task are not visible to the user in either Codex web or the macOS desktop app. The cloud agent repeatedly reports that an image has been displayed, but the conversation contains only text and code.

This affects application screenshots and a small, newly created diagnostic PNG independent of the application.

Environment

  • macOS 26.5.2
  • ChatGPT desktop app in Codex mode; installed app metadata: version 26.908.70816
  • Codex web in Chrome
  • ChatGPT Plus
  • Cloud runtime Node.js 22.22.2

Reproduction

  1. Start a fresh Codex Cloud task.
  2. Create a temporary diagnostic PNG using an available image library.
  3. Ask the agent to actually execute the available image output mechanism, rather than print code:
const result = await tools.view_image({
  path: "/tmp/tailortune-image-transmission-diagnostic-sharp.png"
});
image(result.image_url);

This is executed through functions.exec according to the agent's report.

  1. Inspect the conversation in Codex web and the macOS desktop app.

Expected

An inline image that the user can see.

Actual

No image appears in either interface. The agent states that the native transmission succeeded and that an image appears above its response, but only the response text/code is visible.

The agent's report is not proof that the backend emitted an image payload; please investigate whether the output is lost in tool execution, cloud result transport, or rendering.

Additional context

  • An earlier cloud task successfully launched the website and used a browser automation CLI to create four screenshots. Those screenshots were also never visible to the user.
  • A later task verified successful application startup and HTTP 200, but reported no native local-browser/port-forwarding/artifact tools in its available tool inventory.
  • The minimal PNG test was intended to isolate image delivery from browser capture and application setup.
  • Retesting on the web did not resolve it, so this is not solely a desktop rendering symptom.
  • Proposed sandbox links and a container HTTP server did not provide usable integrated image access.
  • Environment preparation was rerun and the cache reset during troubleshooting.

Related reports:

  • #11081: cloud screenshots visible on web but missing in the desktop app.
  • #16721: screenshots/native screenshot tooling no longer available in Codex web.
  • #17172: screenshot tool unavailable in the environment.

Please confirm the supported mechanism for returning user-visible images from Codex Cloud tasks and investigate this combined web/desktop failure. The intended workflow is integrated visual review of a running cloud application, without publishing screenshots to an external service.

No private repository files, credentials, customer data, or screenshots containing personal information are included in this report.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the minimal PNG flow through functions.exec, tools.view_image, and image(result.image_url) in Codex Cloud, then compare the Codex web and macOS desktop conversations. The issue names no repository files or tests, so trace whether the image payload is emitted by tool execution, transported from the cloud result, or rendered by either client. Done means a supported mechanism reliably produces an inline image in both interfaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, macos, node.js
Domain
backend-api-design, cloud, desktop, web-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.