BUG: Codex multi-account not working over SSH remote (only one provider appears)

[gthay]

Summary

T3Code Version: 0.0.22
Codex multi-account works in local T3 Code, but over SSH remote I cannot get both Codex providers to appear correctly.

Remote environment

• Ubuntu VPS
• SSH user: root

Provider setup

Provider 1:

• Binary path: codex
• CODEX_HOME path: /root/.codex
• Shadow home path: empty

Provider 2:

• Binary path: codex
• CODEX_HOME path: /root/.codex
• Shadow home path: /root/.codex_p

Remote filesystem state

Both auth files exist on the VPS:

/root/.codex/auth.json
/root/.codex_p/auth.json

What I tried

• authenticated both Codex accounts on the VPS
• restarted the server
• restarted T3 Code
• refreshed provider status
• used absolute paths instead of ~

Expected behavior

Both Codex providers should appear and be selectable, as described in the docs:
docs/providers/codex.md

Actual behavior

Only one provider/account appears or the second provider does not show correctly in the SSH environment.

---

Related documentation:
https://github.com/pingdotgg/t3code/blob/main/docs/providers/codex.md

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Thanks for the detailed report. We believe this is fixed by PR #4479.

The v0.0.22 provider settings UI used the primary environment for provider instance reads and writes, even when the user selected an SSH environment. The two remote auth files do not create the second configured provider instance by themselves. PR #4479 routes provider creation, refreshes, reads, and writes to the selected environment.

I'm closing this as fixed as part of an automated pass on all open issues.

If this still happens in a current build that includes PR #4479, please reply with the T3 Code version and fresh logs or reproduction details, and we can reopen it.