Skip to content

Codex Remote on Windows cannot browse drives other than C: or follow junctions #35339

Description

@sukumo28

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.721.41059

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When adding a project folder from Codex Remote on iOS, the remote folder picker starts at:

C:\Users\<user>

It is possible to navigate upward to C:\, but the picker treats C:\ as the filesystem root. At that point, there is no parent-folder action, drive selector, or path input field, so there is no way to navigate to D:\ or any other Windows drive.

The Windows Codex App itself can access projects on D:\, and a D:\ project that I registered previously is still available and works remotely. The problem appears to be limited to adding new projects through the current mobile Remote folder picker.

I also tried creating a directory junction on C:\ that points to a project on D:\.
but the Remote folder picker refuses to browse it and displays:

Could not load folder
This remote folder could not be browsed.

As a result, there is currently no available way to add a new project located on a non-system drive from the mobile Remote interface.

What steps can reproduce the bug?

Steps to reproduce
Use a Windows computer with at least two drives, such as C:\ and D:.
Store a valid Codex project or Git repository on D:.
Enable Remote connections in the Windows Codex App.
Pair an iPhone with the Windows host.
Open Codex Remote in the ChatGPT iOS app.
Start a new chat and select Add new folder from the project picker.
Navigate upward from C:\Users<user> to C:.
Observe that there is no way to navigate above C:, select another drive, or enter an absolute path.
Optionally, create a junction under C:\ targeting the project on D:.
Try to open that junction in the mobile folder picker.
Observe that the folder cannot be loaded.

What is the expected behavior?

Expected behavior
The Remote project picker should support at least one of the following:

  • Show all available Windows drives at the filesystem root.
  • Provide an absolute-path input field, allowing paths such as D:\path\to\project.
  • Allow navigation through valid Windows directory junctions.
  • Show the projects already saved in the connected Windows Codex App.

Additional information

This is not a general access problem with the D:\ drive:
The Windows Codex App already uses multiple projects located on D:.
A D:\ project registered previously is still shown in the mobile project selector and works correctly.
Only newly adding or browsing projects on another drive is blocked.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingiOSIssues related to the Codex iOS appremotewindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions