Reauthentication when switching Business accounts: same workspace vs different workspace

[Jamesgongzx]

I have several ChatGPT Business workspaces, each with multiple accounts:

• Workspace A: a1, a2
• Workspace B: b1, b2
• Workspace C: c1, c2

I understand that v1.21.0 fixed some codex-lb reauthentication problems involving Team seat identity and concurrent token refreshes. I would like to hear about actual experience on v1.21.0 or newer.

1. If one chat switches from a1 to a2 within the same Business workspace, have you experienced reauthentication or account sign-outs?

2. If one chat switches from a1 to b1 across different Business workspaces, have you experienced reauthentication or account sign-outs?

3. Is keeping each chat on one account enough to avoid reauthentication, even when other chats use different accounts or Business workspaces?

4. Which of these workflows has been more reliable?

Option 1: One scoped key per workspace

• Key A is assigned to a1 and a2.
• Key B is assigned to b1 and b2.
• Key C is assigned to c1 and c2.
• Chats initially use Key A.
• When Workspace A is exhausted, switch the Codex client to Key B.
• Use /fork before continuing.
• Repeat with Key C when Workspace B is exhausted.

Option 2: Control workspace selection by pausing accounts

• Use one key that can access all accounts.
• Keep a1 and a2 active.
• Pause the accounts from Workspaces B and C.
• When Workspace A is exhausted, pause a1 and a2.
• Unpause b1 and b2.
• Use /fork before continuing.
• Repeat with Workspace C when Workspace B is exhausted.

Has either workflow caused reauthentication or account sign-outs? Is one more reliable when the accounts belong to different Business workspaces?