codex - 💡(How to fix) Fix Codex Desktop file tree / remote file picker entry point disappeared [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20984Fetched 2026-05-05 05:54:57
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1

In the current Codex Desktop app, the file tree / file explorer UI appears to have disappeared, and the expected remote-file picker entry point is no longer visible.

This makes remote projects much harder to use because there is no obvious way to browse the remote workspace or attach/select files from the remote filesystem.

Root Cause

Remote connections are most useful when the remote filesystem is the source of truth. Without a visible file explorer or remote file picker, remote workflows regress to asking Codex to inspect paths manually, which is slower and less reliable than selecting/browsing files directly.

This is especially painful for large remote repos or remote data/project directories where the user does not already know every relevant path.

Code Example

[features]
remote_connections = true

---

composer.addRemoteFiles
composer.remoteFilePicker.title
thread.fileTreePanel.noMatchingFiles
thread.fileCommandMenu.searchFiles
pullRequestsPage.codeReview.showFileTree
pullRequestsPage.codeReview.hideFileTree
RAW_BUFFERClick to expand / collapse

Summary

In the current Codex Desktop app, the file tree / file explorer UI appears to have disappeared, and the expected remote-file picker entry point is no longer visible.

This makes remote projects much harder to use because there is no obvious way to browse the remote workspace or attach/select files from the remote filesystem.

Environment

  • App: Codex Desktop
  • Version: 26.429.30905
  • Build: 2345
  • Platform: macOS
  • Remote connections enabled in local config:
[features]
remote_connections = true

Remote connections themselves are active: the app can connect to configured SSH hosts and show remote projects/chats.

What Happened

After updating Codex Desktop, the file explorer/file tree option is no longer visible in the app.

I expected to find one of the following:

  • a persistent project file tree / explorer panel;
  • an option in the project/thread UI to open the workspace file tree;
  • a composer + menu option such as Add remote files;
  • a remote file picker for browsing/selecting files from the remote workspace.

However, in the current UI:

  • the file explorer/file tree option is not visible;
  • the composer + menu does not show Add remote files;
  • remote projects/chats are visible, but there is no obvious route to browse or select files from the remote workspace.

Expected Behavior

For a remote project, Codex Desktop should provide a discoverable way to browse or select files from the remote workspace.

At minimum, one of these should be available:

  • a file tree/explorer panel;
  • a project/thread action to browse files;
  • + in the composer -> Add remote files;
  • @ file search that clearly searches the remote workspace.

Actual Behavior

Remote project/chats are visible, but the file tree / file explorer entry point is missing. The composer + menu also does not expose Add remote files.

This leaves the user without an obvious way to inspect or attach remote workspace files from the UI.

Why This Matters

Remote connections are most useful when the remote filesystem is the source of truth. Without a visible file explorer or remote file picker, remote workflows regress to asking Codex to inspect paths manually, which is slower and less reliable than selecting/browsing files directly.

This is especially painful for large remote repos or remote data/project directories where the user does not already know every relevant path.

Notes From Local Inspection

The installed app bundle still appears to contain strings related to file-tree and remote-file UI, including labels like:

composer.addRemoteFiles
composer.remoteFilePicker.title
thread.fileTreePanel.noMatchingFiles
thread.fileCommandMenu.searchFiles
pullRequestsPage.codeReview.showFileTree
pullRequestsPage.codeReview.hideFileTree

So this may be a UI gating/regression issue rather than the code being fully removed from the bundle.

Requested Fix

Please restore a visible, discoverable file explorer / remote file picker entry point for remote projects.

If the file tree was intentionally removed or moved, the UI should expose the replacement path clearly, especially in remote chats where local filesystem assumptions do not apply.

extent analysis

TL;DR

The most likely fix is to restore the file explorer/remote file picker entry point for remote projects, potentially by re-enabling a hidden UI feature or fixing a regression.

Guidance

  • Verify that the remote_connections feature is correctly enabled in the local config file and that the app is properly connected to the remote SSH hosts.
  • Check the app's UI for any hidden or disabled features that may be related to the file explorer or remote file picker, such as a toggle or setting that needs to be enabled.
  • Inspect the app's code or configuration to see if there are any conditional statements or flags that may be causing the file explorer/remote file picker to be hidden or disabled.
  • Test the app with a different remote project or configuration to see if the issue is specific to a particular setup or if it's a more general problem.

Example

No specific code example is provided, but the presence of strings like composer.addRemoteFiles and thread.fileTreePanel.noMatchingFiles in the app bundle suggests that the necessary UI components may still be present, but not visible.

Notes

The issue may be related to a UI regression or a misconfiguration, rather than a complete removal of the file explorer/remote file picker feature. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround by checking the app's UI and configuration for any hidden or disabled features related to the file explorer/remote file picker, as it is likely that the issue is due to a regression or misconfiguration rather than a intentional removal of the feature.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING