openai / openai/codex

Windows Desktop: clicking Canvas after generating an image breaks the chat

Open
#41,203 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug imagen windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using?

Codex Desktop 26.818.5229.0 (Microsoft Store package OpenAI.Codex).

What platform is your computer?

Windows 11 Pro x64, version 10.0.26200 (build 26200).

What issue are you seeing?

After Codex generates an image in a chat, clicking the Canvas button causes the chat UI to break or become unusable. The problem occurs consistently for the reporting user and appears to be tied to the transition from a message containing a newly generated image into Canvas.

No private conversation URL, thread ID, local path, or generated image has been included in this public report.

What steps can reproduce the bug?
  1. Open Codex Desktop on Windows.
  2. Start or open a chat.
  3. Ask Codex to generate an image.
  4. Wait for the image generation to finish and for the image to appear in the conversation.
  5. Click Canvas.
  6. The chat UI breaks / becomes unusable.

The reporting user says this happens every time they follow this sequence.

What is the expected behavior?

Canvas should open normally after an image-generation response, and the existing chat should remain responsive and usable.

Actual behavior

Opening Canvas immediately after generating an image breaks the chat UI.

Additional information
  • Reproducibility: reported as consistent (every attempt).
  • A search of existing open issues found reports about image-heavy threads freezing, but no exact report for the immediate generate image → click Canvas transition.
  • More precise symptoms, screenshots, console logs, or a sanitized thread/feedback ID can be added if maintainers request them.

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

First reproduce the Windows sequence: generate an image in a chat, wait for it to appear, then click Canvas. No file, test, logs, or entry point is named, so trace the Canvas transition from this reproduction. Done means Canvas opens normally and the existing chat remains responsive after the image-generation response.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.