What should I do if provider switching fails on Windows?
First confirm your installed Codus version, then check whether the target provider's terminal is genuinely busy or waiting for input. A “hidden terminal is busy” message is not proof that the latest fix is installed, and an update message printed inside Claude or Codex is not the Codus app version.
Before you start
Save your work. Switching provider should preserve the conversation safely, but it must not interrupt a live command without your decision. Do not delete the project, saved sessions or account credentials to clear a switching error.
Check and recover
- Open Settings → Updates and note Current version. Use Check now and install an available Codus update after saving work.
- Return to the affected quadrant and show Agent. Check any visible terminal for a running command, sign-in prompt or permission question.
- Let genuine work finish, or deliberately stop the specific command if you no longer want it. Do not terminate unrelated terminals.
- Select the intended provider once and watch the switch result. Follow provider switching rather than repeatedly toggling.
- If the same error occurs at an idle prompt on the current release, send support the exact error, Codus version, provider versions and whether you use native Windows or WSL.
A stop-hook error is a separate report about an end-of-turn action. It does not prove the requested work failed, nor that its Done entry or Chat reply was recorded successfully. Check the actual result before retrying the task.
Windows fixes in 0.2.185
Codus 0.2.185 or later fixes account setup failures under a normal Windows user account and command argument errors that could stop Codex Brains and extra project agents from starting. Account setup does not require enabling Developer Mode or running Codus as administrator. Do not delete saved logins or conversations to work around these errors.
This version also fixes idle Windows terminals being reported as busy after resizing a pane or after Claude finishes a reply beside an update notice. These errors could block provider switching, including Codex to Claude. Account checks wait for the terminal to finish redrawing. Brain account switches retry a temporarily unavailable startup check before restoring the previous account. A real running command or unfinished input still needs your attention before switching.
In a narrow Brain pane, Codus could also return to the previous provider while Claude was still restoring the conversation. This version keeps waiting while that work is visible, including when the Brain browser reduces the terminal space.
A queued account switch waits for the current response to finish, including its end-of-turn work. Background inbox messages wait while that switch is queued. Check Switch status for the named terminal's outcome; Cancel switch cancels its queued change. Follow account switching for the difference between a verified current conversation and a manual fallback.
If browser sign-in ends on a localhost connection error, use the Codex sign-in recovery steps. That is a different stage from starting or switching an agent.
If a Brain reports Claude needs you to sign in, open Claude in the bottom status bar and complete + Sign in or Sign in again for the intended account. Then retry the provider change once. This message means the attempted Claude launch explicitly reported that it was not logged in. If the message also says Codex was restored, the failed change returned to Codex; check the conversation with a harmless follow-up before continuing. A generic handoff error alone does not establish a login problem.
How do I know it worked?
The selected provider reaches its working prompt and accepts a harmless follow-up in the expected conversation. A disappearing overlay, changed menu label or green provider-update notice alone is not that confirmation.