Request
Allow ChatGPT Codex mobile to create/register a new local Codex project and start the first thread on a connected desktop host.
Current behavior
Today, mobile can continue local projects that already appear in the project list, but it does not appear to provide a first-class way to bootstrap/register a new local folder from mobile.
In a controlled local comparison:
| creation path |
local state shape |
mobile result |
codex debug app-server send-message-v2 ... from a fresh folder |
source=vscode, thread_source=NULL, originator=Codex Desktop |
folder appeared in ChatGPT Codex mobile |
codex exec -C <folder> ... from a fresh folder |
source=exec, thread_source=user, originator=Codex Desktop |
local session was created, but folder did not appear in ChatGPT Codex mobile |
Token usage was effectively the same in this comparison (23432 vs 23417 total tokens in local rollout evidence), so the practical difference was project registration / mobile visibility rather than cost.
Desired behavior
From ChatGPT Codex mobile, I want to:
- Choose a connected desktop host.
- Select or enter a local folder path on that host.
- Create/register the folder as a Codex project.
- Start the first thread in that project.
Why this matters
Mobile is useful for continuing Codex work remotely, but today I still need to use a desktop/app-server path once before mobile can see a new local project. This makes mobile less useful as a true remote-control surface for starting work.
Suggested implementation
Expose the same registration behavior used by Desktop/app-server-created threads as a first-class mobile action, for example:
- "New local project"
- "Register folder on host"
- "Start thread in folder"
This would avoid requiring users to run codex debug app-server send-message-v2 manually just to make a folder visible from mobile.
Request
Allow ChatGPT Codex mobile to create/register a new local Codex project and start the first thread on a connected desktop host.
Current behavior
Today, mobile can continue local projects that already appear in the project list, but it does not appear to provide a first-class way to bootstrap/register a new local folder from mobile.
In a controlled local comparison:
codex debug app-server send-message-v2 ...from a fresh foldersource=vscode,thread_source=NULL,originator=Codex Desktopcodex exec -C <folder> ...from a fresh foldersource=exec,thread_source=user,originator=Codex DesktopToken usage was effectively the same in this comparison (
23432vs23417total tokens in local rollout evidence), so the practical difference was project registration / mobile visibility rather than cost.Desired behavior
From ChatGPT Codex mobile, I want to:
Why this matters
Mobile is useful for continuing Codex work remotely, but today I still need to use a desktop/app-server path once before mobile can see a new local project. This makes mobile less useful as a true remote-control surface for starting work.
Suggested implementation
Expose the same registration behavior used by Desktop/app-server-created threads as a first-class mobile action, for example:
This would avoid requiring users to run
codex debug app-server send-message-v2manually just to make a folder visible from mobile.