Windows: “Files and folders” picker still opens as file-only after #34965 was completed

Open
#36,080 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the Windows native picker flow behind the composer + menu's “Files and folders” option, then compare its behavior with the completed work in #34965. Confirm that selecting a folder attaches it as context rather than entering it, while file selection continues to work.

Written by the indexing model from the issue text.

Description

app bug windows-os
Summary

This appears related to #34965, which was marked completed, but I can still reproduce the issue on Windows as of July 29, 2026.

The composer + menu says "Files and folders", but the native Windows picker behaves like a file-only picker. Selecting a folder enters the folder instead of attaching it as context.

Dragging a folder into the composer/source area still works as a workaround.

Steps to reproduce
  1. Open the Codex desktop app on Windows.
  2. In a conversation, click the composer + button.
  3. Choose "Files and folders".
  4. In the Windows picker, select a folder.
  5. Click "Open".
Expected behavior

The selected folder should be attached as folder context.

Actual behavior

The picker enters the folder instead of attaching it. The flow only allows choosing files.

Related issue

Related to #34965, but still reproducible for me after that issue was marked completed.

Environment
  • OS: Windows
  • Codex desktop app version: unknown
  • Reproduced on: July 29, 2026
  • Feedback/thread id: 019fade7-91d6-7e73-8f5c-1a3f3640536f
Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

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.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.