Remote Control threads created from MacBook are not visible in the host Mac mini Codex Desktop sidebar

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

26.803.81509

What subscription do you have?

Pro 20x

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

What issue are you seeing?

I use Codex Desktop on two Macs signed into the same account:

• Host: Mac mini running Codex Desktop with Remote Control enabled
• Controller: MacBook running Codex Desktop
• Connection: MacBook -> Connections -> Mac-mini-Neo.local

Remote Control itself works correctly.

When I create a new thread from the MacBook under the connected
Mac-mini-Neo.local environment, the thread executes correctly on
the Mac mini.

I verified this by running:

hostname
pwd
echo $HOME

The commands return the Mac mini hostname, filesystem path and home
directory, confirming that execution happens on the remote Mac mini.

However, the thread created through Remote Control does NOT appear
in the "Local" thread list/sidebar of Codex Desktop running directly
on the Mac mini.

The thread remains visible on the MacBook under:

Connections
-> Mac-mini-Neo.local
->

This means the same Mac mini app-server appears to have two different
thread discovery/indexing views:

1. Threads visible through Remote Control
2. Threads visible in the host Codex Desktop local sidebar

Steps to reproduce

1. Install/run Codex Desktop on a Mac mini.
2. Enable Remote Control on the Mac mini.
3. On another Mac running Codex Desktop, connect to the Mac mini via:
   Connections ->
4. Create a new thread under the remote Mac mini connection.
5. Run:
   hostname
   pwd
   echo $HOME
6. Confirm that the commands execute on the Mac mini.
7. Open Codex Desktop directly on the Mac mini.
8. Check the Local threads/sidebar.

Actual behavior

The Remote Control-created thread is visible on the MacBook under
the Mac mini connection, but it is missing from the Codex Desktop
sidebar on the Mac mini itself.

Expected behavior

A thread executing on the Mac mini through its Codex app-server should
be discoverable and resumable from Codex Desktop running directly on
that Mac mini.

Remote Control should provide another client/view of the same host
threads rather than creating threads that the host Desktop UI cannot
discover.

This is especially important for always-on Mac mini workflows:

MacBook -> Remote Control -> Mac mini

I expect to be able to start work remotely from the MacBook and later
sit down at the Mac mini and continue the same thread locally.

Additional information

Remote execution itself works correctly. This does not appear to be
a connectivity or authentication issue.

The problem appears limited to thread persistence/discovery/sidebar
hydration between Remote Control and the host Desktop UI.

Related issues:

#35881 - Remote project threads disappeared from Codex sidebar
#34922 - Remote Control threads reachable by ID but not discoverable
#25482 - Support remote app-server threads in Desktop thread orchestration

What steps can reproduce the bug?

I use Codex Desktop on two Macs signed into the same OpenAI account.

Environment:

• Host machine: Mac mini
• Client machine: MacBook
• Codex Desktop is installed and running on both machines
• Remote Control is enabled on the Mac mini
• The MacBook connects to the Mac mini through:
  Connections -> Mac-mini-Neo.local

Steps to reproduce:

1. Start Codex Desktop on the Mac mini.
2. Enable Remote Control on the Mac mini.
3. Open Codex Desktop on the MacBook.
4. Connect to the Mac mini through:
   Connections -> Mac-mini-Neo.local
5. Create a new thread from the MacBook under the remote Mac mini connection.
6. In that remote thread, run:

hostname
pwd
echo $HOME

7. Verify that the commands are executed on the Mac mini. In my case, hostname, pwd, and $HOME all point to the Mac mini environment.
8. Confirm that the thread is visible on the MacBook under:
   Connections -> Mac-mini-Neo.local
9. Now open Codex Desktop directly on the Mac mini.
10. Check the "Local" threads in the sidebar.
    Actual behavior:
    The thread created from the MacBook through Remote Control is not visible in the Codex Desktop sidebar on the Mac mini.
    The thread is still visible and usable from the MacBook, and commands in that thread continue to execute on the Mac mini correctly.
    This means Remote Control execution works, but the thread created through Remote Control is not discoverable from the Codex Desktop UI running directly on the host machine.
    I reproduced this with multiple remote threads.
    Session ID: not available
    Token limit usage: not applicable
    Context window usage: not applicable

What is the expected behavior?

A thread created through Remote Control and executed on the Mac mini should also be visible and resumable from Codex Desktop running directly on that same Mac mini.

Expected workflow:

1. I create Thread A from Codex Desktop on my MacBook.
2. Thread A is created under the remote connection to the Mac mini.
3. Thread A executes on the Mac mini.
4. Later, I open Codex Desktop directly on the Mac mini.
5. Thread A should be visible in the sidebar and I should be able to continue the same thread locally.

In other words, Remote Control should behave as another client connected to the same Codex host and thread state.

Expected state:

MacBook Codex Desktop
-> Connections
-> Mac-mini-Neo.local
-> Thread A

and at the same time:

Mac mini Codex Desktop
-> Local
-> Thread A

The same thread should be discoverable from both clients because the execution environment and host are the same Mac mini.

Additional information

Remote execution itself works correctly.

I verified this by running:

hostname
pwd
echo $HOME

from the remote thread created on the MacBook.
The output confirms that the commands are executed on the Mac mini, not on the MacBook.
So this does not appear to be a Remote Control connectivity or execution issue.
The issue appears to be specifically related to thread discovery, indexing, sidebar synchronization, or persistence visibility between:

• Codex Desktop connected through Remote Control
• Codex Desktop running directly on the remote host
  My intended workflow is:
  MacBook
  -> Codex Desktop
  -> Remote Control
  -> always-on Mac mini
  I want to start a task remotely from the MacBook, then later sit at the Mac mini and continue the exact same Codex thread locally.
  Currently this is not possible because Remote Control-created threads are missing from the host Mac mini sidebar.
  I am attaching two screenshots:

1. MacBook: Mac-mini-Neo.local is connected and the remote threads are visible.
2. Mac mini: the same remote threads are missing from the "Local" thread list.

Reproduce the flow using Remote Control between the MacBook and Mac mini, then compare the remote connection thread list with the host's Local sidebar after running hostname, pwd, and echo $HOME. Investigate the thread discovery, indexing, persistence, or sidebar synchronization entry points implicated by the report. Done means a thread created remotely is visible and resumable in the host Mac mini's Local list.