[Desktop/iOS Remote] New worktree ignores configured git-worktree-root

Summary

A fresh Git worktree created from ChatGPT iOS Remote on a connected macOS host is placed under the default ~/.codex/worktrees root, even though the host has a different git-worktree-root configured.

This is a creation-location problem, not an existing-thread handoff/reuse issue.

Environment

• macOS host running ChatGPT/Codex Desktop 26.915.31029
• Bundled Codex session version: 0.155.0-alpha.2.6
• Flow: ChatGPT iOS Remote -> connected macOS host -> new task in Worktree mode
• Host configuration: git-worktree-root = "~/code/worktrees"

Steps to reproduce

1. On the macOS host, set Settings > Worktrees > Worktree root to a non-default path (in this case ~/code/worktrees).
2. From ChatGPT on iOS, connect to that host through Remote.
3. Start a new task in Worktree mode for an existing local Git project.
4. Inspect the resulting worktree on the host with git worktree list.

Expected

The new worktree is created below the configured root, e.g. ~/code/worktrees/<id>/<repo>.

Actual

The fresh worktree was created under the default location:

~/.codex/worktrees/<generated-id>/<repo>

The affected worktree was created at the time of the remote request and is a detached-HEAD managed worktree, so this was not an old associated worktree being reused.

Additional context

OpenAI documentation says Remote worktrees require a connected computer and follow workspace settings. This result appears to contradict that behavior.

Possibly related (same iOS Remote creation path, but a different symptom): #23418. That issue is about Desktop sidebar/project association; this report is specifically about the configured worktree root being ignored.

I have intentionally redacted the username, repository name, session ID, and exact absolute paths.

Start by tracing the new Worktree-mode creation request from ChatGPT iOS Remote through the connected macOS host, focusing on how the configured git-worktree-root is read and passed to worktree creation. Reproduce the flow and inspect the result with git worktree list; done means fresh worktrees use the configured root rather than ~/.codex/worktrees.