Identify the symptom.
Recover the bridge in order.

Symptom

Launch Browser shows no window or returns to its initial state.

Likely cause

The browser process could not start, a previous instance is stuck, or Windows blocked the launch.

Solution

1. Wait for the launch state to finish.
2. Close only controlled-browser windows that remain stuck.
3. Press Launch Browser once more.
4. If it fails again, close MIMETOR, reopen it and retry.

Symptom

The browser opens but remains blank, shows a network error, or never reaches ChatGPT/Qwen.

Likely cause

Unstable connection, network filtering, DNS, proxy, VPN, or a temporary provider outage.

Solution

1. Confirm other secure websites load in Windows.
2. Temporarily disable a VPN or proxy only if your policy allows it.
3. Reload the provider page.
4. Check the provider public status and retry after recovery.

Symptom

MIMETOR reports no detected session even though the browser is open.

Likely cause

Authentication did not finish, the session expired, consent is pending, or another browser profile was opened.

Solution

1. Return to the window launched by Cloud Brain.
2. Complete any login, verification, or consent requested by the provider.
3. Confirm the chat input is visible.
4. Return to MIMETOR and press Verify Login.

Symptom

The session is verified, but the bridge remains off or unavailable.

Likely cause

The bridge is not covered by the local license, another provider is selected, or initial setup is incomplete.

Solution

1. Open License and confirm that bridge is active on this device.
2. Return to Cloud Brain and select the same provider.
3. Verify the session again.
4. Run Setup if the project is shown as incomplete.

Symptom

Run Setup keeps loading, ends with an error, or does not confirm the project.

Likely cause

Invalid session, unexpected provider page state, a temporary service limit, or an interruption while uploading sources.

Solution

1. Do not press Run Setup repeatedly.
2. Confirm the provider page responds and Verify Login succeeds.
3. Wait for any pending upload to finish.
4. Run Setup once more.
5. If it fails again, restart MIMETOR and begin again at Launch Browser.

Symptom

The chat remains waiting, receives no reply, or stops progressing after an action.

Likely cause

The provider is still generating, displayed an additional choice, lost connectivity, or the session became invalid.

Solution

1. Check the provider window for a required choice or confirmation.
2. Wait for an active response to finish.
3. If it is stuck, reload the provider page.
4. Verify the session again and resume from the MIMETOR chat.

Symptom

The chat tries to use ChatGPT when Qwen was intended, or vice versa.

Likely cause

The chat kept its previous provider or single-bridge mode remains active.

Solution

1. Check the provider name in the chat header.
2. With Dual Cloud Brain, select it in that header.
3. Without dual mode, open Cloud Brain and activate the correct bridge.
4. Verify the new provider session before continuing.

Symptom

The dual control is disabled or absent.

Likely cause

Dual Cloud Brain requires active licenses for both ChatGPT and Qwen bridges.

Solution

1. Open License and check current coverage.
2. Purchase and activate the missing bridge or the complete pack.
3. Refresh license status.
4. Return to Cloud Brain and enable dual mode.

Symptom

Launch Browser, Verify Login, Run Setup, or another bridge action cannot be pressed.

Likely cause

A previous requirement is missing, another operation is running, or the license does not cover the bridge.

Solution

1. Read the status shown beside the bridge.
2. Confirm the license and selected provider.
3. Wait for the current operation to finish.
4. Complete Launch Browser → Verify Login → Run Setup in order.

Symptom

The page appears accessible, but MIMETOR keeps an old or contradictory state.

Likely cause

The provider interface changed, the page only partially loaded, or the check ran too early.

Solution

1. Wait for the page to finish loading.
2. Reload the provider once.
3. Press Verify Login again.
4. If it persists, restart MIMETOR and reopen the controlled browser.