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.
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.