[bug] Account switching works in Codex CLI but not in the Codex app

[adithya04dev]

Summary

Switching accounts via codex-multi-auth appears to work for the Codex CLI, but the Codex desktop app does not pick up the switched account.

Actual behavior

• Switching accounts affects CLI usage as expected
• The Codex app does not reflect the switched account / continues behaving as if the previous account is still active

Expected behavior

• After switching accounts with codex-multi-auth, both the CLI and the Codex app should use the newly selected account consistently

Reproduction

1. Configure multiple accounts in codex-multi-auth
2. Switch to another account
3. Confirm the new account is used from the CLI
4. Open or use the Codex desktop app
5. Observe that the app does not switch along with the CLI

Notes

This looks like account switching is currently wired correctly for CLI flows, but not for the Codex app path.

If needed, I can provide environment details or logs in a follow-up comment.

[adithya04dev]

I dug through the docs and want to confirm the expected behavior for app-bind / runtime rotation.

I'm seeing this sequence locally:

• codex-multi-auth switch 1 reports a successful switch to account 1
• codex-multi-auth status then shows account 1 as selected / best
• but later codex-multi-auth status reports:
  • Last runtime account: Account 2
  • Runtime in use: account 2 (app-bind)

From the docs, I understand the Codex desktop app can be bound to the local runtime proxy and the app UI may show codex-multi-auth rather than the actual account.

What I'd like to confirm is:

1. When I manually run codex-multi-auth switch <index>, is the desktop app expected to be pinned to that account for subsequent requests?
2. Or is app-bind intentionally allowed to route each request through any healthy account in the pool, even after a manual switch?
3. If rotation is expected, what exactly does switch control for the desktop app path: default preference, sticky session affinity, or only CLI auth state?
4. If the app should honor the manual switch, is Runtime in use: account 2 (app-bind) after switching to account 1 a bug?

I'm mainly trying to distinguish between:

• expected runtime rotation behavior
• versus a real app-bind sync issue between selected account and actual request account.