Why does ChatGPT for Android say it can't verify project trust for Codex worktrees?

Remote connections between the ChatGPT Android app (v 1.2026.237 (16)) and a MacBook M4 running ChatGPT Version 26.825.51511 are hitting a wall with project trust verification. Specifically, users are seeing a blocking error when trying to access paths like /Users/<user>/.codex/worktrees/<id>/<project>. The system claims it cannot verify the trust status of the repository and tells the user to open the repo in Codex on the remote machine to make a trust choice.
The frustrating part is that the repository is often already open in Codex on the remote Mac, yet the trust prompt never triggers, leaving the Android client stuck. This doesn't happen across the board; it seems to trigger randomly for certain projects, specifically when initializing a new worktree or occasionally while staying on the main branch.

How to handle the project trust error

When you encounter the message "Can’t verify project trust... Open the repository in Codex on the remote computer and make a trust choice," the standard advice is to manually trigger the trust dialog. However, since the repo is already open, the app fails to recognize the existing state.
If you are stuck in this loop, try these specific steps:

1. Force a Read-Only Session: The error message suggests starting in Read-only mode. This is the fastest way to bypass the trust check if you only need to review code without making edits via the Android app.
2. Verify the Original Directory: Ensure that the path selected on the remote computer matches the exact directory the Android app is requesting. If you are using worktrees, the path is nested deep in .codex/worktrees/, which might differ from where you typically open the project.
3. Trigger a Trust Refresh: Since the prompt isn't appearing, try closing the project in Codex on the MacBook M4 entirely, deleting the local trust cache for that specific worktree, and reopening it to force the "Do you trust the authors of the files in this folder?" popup.
4. Version Sync: Check if the Codex installation on the remote machine is outdated. The error explicitly states that updating Codex on the remote computer may resolve persistent verification failures.

Why the trust mechanism fails in worktrees

The root of the problem likely lies in how Codex handles Git worktrees compared to standard repositories. In a standard setup, the trust is tied to the root folder. With worktrees, the files reside in a separate directory under .codex/worktrees/ID/PROJECT, but they share the same .git history.
The Android app is looking for a trust flag associated with the specific worktree path, but the remote Codex instance likely only registered trust for the main repository folder. Because the trust isn't inherited or mirrored across all worktree paths, the Android client sees the worktree directory as "untrusted" and blocks the connection.

When to move to read-only mode

If you have verified that Codex is updated to Version 26.825.51511 and the project is open, but the trust prompt still won't appear, you have to weigh the risk of Read-only mode.
Read-only mode is a viable fallback when:

• You are in a rush and only need to read a specific function or configuration file.
• You are working on a main branch where trust was previously established, but the system has suddenly "forgotten" the status.
• You are troubleshooting a new worktree and cannot figure out why the remote machine isn't flagging the trust choice.

The risk here is purely productivity; you lose the ability to push changes or execute remote commands from your mobile device. If you need full write access, the only real solution is to find a way to force the remote Codex instance to explicitly trust the specific sub-directory within the .codex/worktrees/ path. Until a patch is released for v 1.2026.237 (16) or the Mac desktop version, this manual path verification remains the only workaround.