Feature request: create/register a new local Codex project and first thread from mobile

Open 💬 1 comment Opened Jun 13, 2026 by Celob185

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:

  1. Choose a connected desktop host.
  2. Select or enter a local folder path on that host.
  3. Create/register the folder as a Codex project.
  4. 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.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗