openai / openai/codex

[Windows/Android Remote] Scheduled automation threads never appear on Android while normal threads in the same project do

Open
#44,133 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app automations bug remote windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.903.61454

What subscription do you have?

Plus

What platform is your computer?

Windows 10

What issue are you seeing?

Summary

Scheduled automation/task runs created by the Codex desktop app on a Windows host do not appear in Codex Remote on the ChatGPT Android app.

Normal manually created Codex chats in the exact same project appear correctly on Android Remote.

This is consistently reproducible: normal chats sync, but none of the conversations/threads created by scheduled tasks are visible on Android.

Environment
Host: Codex desktop app on Windows
Remote client: ChatGPT Android app using Codex Remote
Same ChatGPT account on both devices
Codex desktop version: [fill in from About Codex]
ChatGPT Android version: [fill in if available]
Subscription: [Plus / Pro / other]
What issue are you seeing?

I have scheduled tasks/automations configured inside a Codex project on my Windows PC.

The scheduled tasks execute successfully. Their resulting conversations/threads are visible in the Codex desktop application.

However, those scheduled-task conversations never appear when I connect to that same computer and project using Codex Remote from the ChatGPT Android application.

Other chats in the same project work correctly.

For example:

Manually create Chat A in the project on Windows → appears on Android Remote.
Scheduled task executes and creates Chat B in the same project → does NOT appear on Android Remote.
Manually create Chat C afterward → appears on Android Remote.

I have multiple scheduled tasks/chats and none of their generated threads appear on Android.

Because manually created conversations before and after the scheduled run appear correctly, this does not appear to be a general Remote connection, account, host, or project synchronization problem.

It appears specifically related to how automation/scheduled-run threads are included in the thread list exposed to Android Remote.

What steps can reproduce the bug?

Steps to reproduce
Open the Codex desktop app on Windows.
Open an existing Codex project that is accessible through Android Remote.
Manually create a normal chat/thread in that project.
Connect to the Windows computer using Codex Remote in the ChatGPT Android app.
Confirm that the manually created thread appears on Android.
Configure or run a scheduled task/automation associated with the same Codex project.
Allow the scheduled task to complete.
Confirm that the resulting scheduled-run conversation/thread exists in the Codex desktop app.
Open or refresh the same project through Codex Remote on Android.
Observe that the scheduled-run thread is missing.
Create another normal manual chat in the project on Windows.
Refresh Android Remote.
Observe that this new manual chat appears while the scheduled-run chat remains missing.

This behavior occurs consistently across scheduled runs.

What is the expected behavior?

Actual behavior

Normal interactive Codex threads synchronize from the Windows host to Android Remote.

Threads generated by scheduled tasks/automations do not appear in Android Remote at all.

Example:

Windows Codex project:

Manual thread #1 → Android: visible
Manual thread #2 → Android: visible
Scheduled automation thread → Android: MISSING
Manual thread #3 → Android: visible
Scheduled automation thread → Android: MISSING

The scheduled threads remain available on the Windows Codex host.

Expected behavior

A scheduled automation run creates a legitimate Codex conversation/thread on the host.

If Android Remote exposes conversations from that Codex project, scheduled-run threads should also be discoverable and accessible from Android Remote just like manually created threads.

The source of the thread (interactive vs. automation) should not prevent the user from accessing the completed conversation remotely.

Additional information

Why this appears specific to automation threads

The Windows host, Android Remote connection, account, and Codex project are all functioning.

Manually created threads in the same project synchronize correctly both before and after a scheduled automation runs.

Only automation-generated threads are consistently omitted.

This suggests that the Android Remote thread listing may be filtering threads based on their source/type and returning interactive conversations while excluding automation-generated conversations.

Related issue

Possibly related to:

#41470 — "[Windows/Android Remote] New desktop projects/threads do not appear on mobile"

https://github.com/openai/codex/issues/41470

That issue concerns broader Windows-to-Android Remote thread/project discovery.

This report is more specific: the project and ordinary desktop-created threads ARE visible on Android. Only scheduled automation-created threads are consistently missing.

Impact

This makes scheduled Codex tasks much less useful remotely.

One of the main benefits of scheduled tasks is allowing Codex to perform work automatically and then reviewing the results later. Currently I can see those results on the Windows Codex host, but cannot review the generated conversations from my Android phone through Codex Remote.

Additional information

I can provide screenshots showing:

The Windows Codex project containing normal and scheduled-run conversations.
The same project's Android Remote conversation list where the normal conversations are present but the scheduled-run conversations are missing.
Scheduled-task configuration and successful execution.

I can also provide exact Codex desktop and Android app versions if needed.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files or tests are named. Reproduce with a Windows project containing both manual and scheduled-run threads, then trace the remote thread-list path used by the Android client and compare how those thread types are represented or filtered. Done means scheduled-run conversations appear alongside manual threads in Android Remote without breaking existing synchronization.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, rust
Domain
backend-api-design, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.