Codex Desktop should show remote-created sessions in the normal sidebar

[Dreamzhc328]

Summary

Codex Desktop should show remote-created sessions hosted on the current machine in the normal conversation sidebar without requiring a restart or local state workaround.

Setup

• Codex Desktop is installed on multiple Macs.
• Remote-control is enabled so one device can create a remote session on another target Mac.

Observed behavior

• The target Mac receives the remote-created session.
• The thread exists locally and can be opened directly by thread id.
• The normal Codex Desktop conversation sidebar does not reliably show that remote-created session live.
• In practice, the session may only become visible after restarting Codex Desktop or manually refreshing local sidebar state.

Expected behavior

• If a remote-created session is hosted on the current machine, Codex Desktop should show it in the same normal conversation sidebar as locally-created sessions.
• The sidebar should refresh from the local thread store or app-server thread-start events when the remote thread lands.
• The UI can still show origin/host/environment metadata, but users should not need polling scripts, manual state edits, or app restarts.

Related remote-control issue

• New or repaired remote-control enrollments now appear to require MFA.
• If MFA setup is blocked by account state, users may be unable to re-enroll devices even though existing grandfathered enrollments still work.
• A clearer recovery path and error message would help.

Product request

1. Automatically include remote-created sessions hosted on the current machine in the sidebar.
2. Trigger sidebar refresh from thread DB/app-server events when a remote session starts.
3. Show small origin/host/environment metadata for clarity.
4. Document remote-control enrollment recovery when MFA setup is unavailable.

Why this matters

Remote-control is only useful if the target machine's Desktop UI becomes a reliable control plane. Today it can look like session creation failed even when the backend and local thread store succeeded.

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• Desktop sidebar does not show local threads created through app-server #30895
• Desktop never resumes threads that appear while the app is running (created by an external app-server client) - endless loading, resumeState=null, until app restart #30916

Powered by Codex Action

[Dreamzhc328]

Closing this as a duplicate of #30895. The remote-created-session/sidebar behavior matches that issue; the MFA re-enrollment/recovery note is a separate remote-control recovery topic and can be tracked separately if needed.