›_ Codex Issues
Codex Issues / #37615

Windows app: Download Plan succeeds silently with no confirmation or destination feedback

Open 💬 1 comment Opened Aug 8, 2026 by bygiro

Codex App version

26.727.6591.0 (OpenAI.Codex, Windows AppX)

Platform

Windows x64

Issue

In Plan mode, clicking Download Plan successfully writes PLAN.md to the user's Downloads folder, but the app shows no visible success confirmation, filename, destination, or failure state.

This makes a successful download look like a failed action. Repeated clicks then create silent duplicates such as PLAN (1).md, PLAN (2).md, and so on.

Steps to reproduce

  1. Open the Codex desktop app on Windows.
  2. Switch to Plan mode and generate a completed plan.
  3. Click Download Plan.
  4. Observe that no toast, banner, save dialog, filename, or destination is shown.
  5. Click the button again because the first click appears to have done nothing.
  6. Inspect the Windows Downloads folder and find multiple numbered copies of the plan.

Verified behavior

The files were present and valid UTF-8 Markdown, confirming that this is a feedback/discoverability problem rather than a filesystem-permission or download-integrity failure.

Expected behavior

After a successful download, show a clear confirmation such as:

Plan downloaded as PLAN.md

with actions such as Open file and Open folder. If a numbered duplicate is created, show the actual filename. If the write fails, show an actionable error.

A Save as option would also make the destination explicit.

View original on GitHub ↗

1 Comment

noodles-chen · 16 days ago

I can reproduce the same issue on macOS.

Environment

  • Codex app: 26.803.61601 (bundle build 6396)
  • macOS: 26.3.1 (25D2128)
  • Architecture: Apple Silicon, Apple M4

Observed behavior

Clicking Download Plan produces no toast, save dialog, filename, destination hint, or other visible response. Because the button appears to do nothing, I clicked it repeatedly.

A filesystem check confirmed that the downloads had actually succeeded silently:

  • PLAN.md
  • PLAN (1).md
  • PLAN (2).md
  • PLAN (3).md
  • PLAN (4).md

All five files were valid Markdown, had the same 6,702-byte size, and had the same SHA-256 hash. The files were created within roughly 13 seconds, matching the repeated button clicks.

So this is reproducible on macOS as well and is specifically a missing success/destination feedback issue, not a download or file-integrity failure.

A success toast containing the actual filename and an Open in Finder action would prevent users from assuming the click failed and creating duplicate files.