Remote Control tasks remain visible after account switch while their projects disappear

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

26.810.52044 (build 6662); bundled codex-cli 0.148.0-alpha.9

What subscription do you have?

Unknown. This reproduction used two ChatGPT accounts with different remaining Codex usage.

What platform is your computer?

Controller: Darwin 24.6.0 arm64 arm

Remote host: Apple-silicon Mac mini, macOS 26.5.2

What issue are you seeing?

After switching the Codex Desktop controller from account A to account B, Remote Control remains connected and the historical task inventory from the remote Mac remains visible, but the saved remote projects disappear because their visibility is account-scoped.

The same tasks that previously belonged to named projects are then surfaced with no project association. In a backend list response they have projectId: null, even though their working directories still point into the original project/worktree paths on the remote host.

This creates an inconsistent authorization and navigation state:

• Remote host and historical tasks remain visible across the account switch.
• Saved remote projects do not remain visible.
• Tasks are removed from their project groupings but remain openable/actionable.
• The UI does not explain that tasks and projects are being resolved under different scopes.

No files need to be modified to reproduce this.

What steps can reproduce the bug?

1. Sign into Codex Desktop with account A.
2. Enable Remote Control for a Mac host and create tasks inside saved projects on that host.
3. Confirm the tasks appear under their projects on the controller.
4. Sign out of account A on the controller and sign into account B.
5. Observe that Remote Control remains connected and the remote tasks remain visible.
6. Observe that the saved project list no longer contains the projects created under account A.
7. Observe that the historical remote tasks now appear outside their projects with no visible explanation of the scope mismatch.

What is the expected behavior?

Remote host, task, and project visibility should use a coherent scope. If tasks intentionally remain machine-scoped while projects are account-scoped, Desktop should not present those tasks as normally actionable orphaned tasks. It should explain the account mismatch and provide a safe re-association or read-only state.

Additional information

This is related to, but distinct from, #32173. That report covers active threads retaining stale account credentials after an explicit account switch. This report is about the task/project visibility model becoming internally inconsistent before a new turn is sent.

The report intentionally omits account IDs, hostnames, environment IDs, and task contents.