You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Codex Handoff cannot detect an already saved Windows project #38872
What version of the Codex App are you using (From “About Codex” dialog)?
26.810.52044
What subscription do you have?
plus
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
I am using Codex Desktop on macOS and attempting to hand off an existing local Git project task to a connected Windows remote host.
Both the macOS source host and the Windows destination host have saved local projects that point to the same Git repository. The Windows project is recognized as a Git repository, and the destination host is online and signed in to the same ChatGPT account and workspace.
When I initiate Handoff from macOS, the Windows host either does not appear in the run-location selector or the handoff fails immediately with:
No matching saved project was found on .
I expected the destination host to be available because its project is already saved and associated with the same Git repository.
Steps already attempted:
Recreated the saved project on the Windows host
Created a new project record with a different display name
Confirmed that both projects use the same Git repository
Confirmed that the Windows host is online
Restarted/reconnected the desktop apps
No project files were modified while reproducing this issue.
Reproduced on 2026-10-13 with a macOS controller and a paired Windows destination. Adding current-version diagnostics because the saved-project lookup appears to be the failing boundary.
Environment
ChatGPT/Codex desktop on the Mac: 26.1007.21159, build 20052, bundle identifier com.openai.codex.
Bundled Mac runtime: codex-cli 0.162.0-alpha.17.2.
macOS: 26.6.2 (25G83).
Destination: Windows 11 Pro, build 26200, connected through the desktop app's paired-device Remote Control connection. The Windows app's exact version was not collected.
Reproduction and observations
Save a local project for the same Git repository on both computers, using each checkout's repository root.
Verify the Windows project is visible in the destination app's sidebar and that its saved rootPaths points to the existing Windows checkout.
Verify git rev-parse --show-toplevel and git remote -v at the Windows saved-project path. Both hosts use their repository root and exactly the same HTTPS origin URL.
The call immediately returns No matching saved project was found on <Windows host>. No operation ID is created and no transfer starts.
The Mac's list_projects({}) returns only Mac-local projects. An explicit read_thread call with the Windows hostId successfully reads an existing Windows chat whose working directory is the saved Windows repository root. The destination installation's environment ID was also checked against the paired host ID; this is the correct host, not a different connection.
Refreshing the connection did not resolve the failure. Temporarily associating the source chat with the saved Mac project did not resolve it either; that association was restored afterward. The source chat and its Git changes remain intact.
Potential cause — inference from the installed Mac app
The handoff preflight obtains destination roots through workspace-root-options, then matches Git origins and repository-relative paths. For paired remote hosts, the installed app's project manager appears to derive those roots from the controller's saved remote-project entries, rather than the destination app's saved local-project entries. In this reproduction the controller's remote-projects collection is empty, while the Windows app has a valid saved local project.
This suggests a missing remote-project binding/discovery step. Adding a controller-side remote binding has not been tested, so this is a suspected cause, not a verified workaround.
Expected behavior
The destination's saved matching Git project should be discoverable for handoff, as described in the remote connections guidance. If a separate controller-side remote-project registration is required, the error should identify that requirement and offer an actionable way to register the existing folder.
Repository URLs/names, user paths, device names, environment IDs, and chat IDs are intentionally redacted. No full logs or session transcripts are attached.
Activity
github-actions commentedon Aug 16, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
rob-didio commentedon Oct 13, 2026
Reproduced on 2026-10-13 with a macOS controller and a paired Windows destination. Adding current-version diagnostics because the saved-project lookup appears to be the failing boundary.
Environment
com.openai.codex.codex-cli 0.162.0-alpha.17.2.Reproduction and observations
rootPathspoints to the existing Windows checkout.git rev-parse --show-toplevelandgit remote -vat the Windows saved-project path. Both hosts use their repository root and exactly the same HTTPS origin URL.{ "threadId": "<source-chat-id>", "destinationHostId": "remote-control:<paired-windows-host>" }handoff_thread.No matching saved project was found on <Windows host>.No operation ID is created and no transfer starts.The Mac's
list_projects({})returns only Mac-local projects. An explicitread_threadcall with the WindowshostIdsuccessfully reads an existing Windows chat whose working directory is the saved Windows repository root. The destination installation's environment ID was also checked against the paired host ID; this is the correct host, not a different connection.Refreshing the connection did not resolve the failure. Temporarily associating the source chat with the saved Mac project did not resolve it either; that association was restored afterward. The source chat and its Git changes remain intact.
Potential cause — inference from the installed Mac app
The handoff preflight obtains destination roots through
workspace-root-options, then matches Git origins and repository-relative paths. For paired remote hosts, the installed app's project manager appears to derive those roots from the controller's saved remote-project entries, rather than the destination app's saved local-project entries. In this reproduction the controller'sremote-projectscollection is empty, while the Windows app has a valid saved local project.This suggests a missing remote-project binding/discovery step. Adding a controller-side remote binding has not been tested, so this is a suspected cause, not a verified workaround.
Expected behavior
The destination's saved matching Git project should be discoverable for handoff, as described in the remote connections guidance. If a separate controller-side remote-project registration is required, the error should identify that requirement and offer an actionable way to register the existing folder.
Repository URLs/names, user paths, device names, environment IDs, and chat IDs are intentionally redacted. No full logs or session transcripts are attached.