Remote-control daemon host does not show existing CLI/TUI sessions in project history, while SSH connection can see them

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

26.616.71553

What subscription do you have?

GPT Pro (100$)

What platform is your computer?

Darwin 25.2.0 arm64 arm

What issue are you seeing?

I’m seeing a session visibility problem between the SSH remote control and the newer remote-control daemon.

On a Linux remote host, I have existing Codex CLI/TUI sessions created directly on that server. These sessions are still present and resumable:

codex resume --all

shows the expected historical sessions.

When I connect to the same server through Codex Desktop using the SSH connection, those existing conversations are visible for the relevant project/directory.

However, when I start the remote-control daemon on the same server and connect to it from Codex Desktop through Settings > Connections > Control other devices, the same project/directory does not show those existing CLI/TUI conversations.

The remote-control daemon is running under the same user and same default CODEX_HOME as the original CLI/TUI sessions.

Environments

Remote host:

Linux 6.8.0-124-generic x86_64 x86_64
codex version: codex-cli 0.141.0
daemon start command: codex app-server daemon bootstrap --remote-control

Local Desktop App:

Darwin 25.2.0 arm64 arm
version: 26.616.71553

What steps can reproduce the bug?

No idea what's the problem

What is the expected behavior?

The history can be seen in both ways.

Additional information

_No response_