Troubleshooting

Always start here: `Mosayic: Show Logs`

Run Mosayic: Show Logs from the Command Palette. This opens the “Mosayic WebSocket” output channel where the extension writes everything: sign-in events, connection attempts, every command it received, every command it ran, every error it hit.

Most issues are visible in the first ten lines of the logs. Sensitive values are auto-redacted, so you can usually share the log contents directly with support if needed.

Status bar shows “signed out”

You’re not signed in.

Run Mosayic: Sign In from the Command Palette.
The browser should open to Google OAuth. If it doesn’t, check that no popup blocker intercepted it.
Use the same Google account you use on the dashboard.

If sign-in opens the browser but never returns to VS Code:

Make sure VS Code is the registered handler for the vscode:// URI scheme. On macOS, opening a vscode:// URL from the terminal should open VS Code:
Terminal window
```
open "vscode://"
```
Some Linux desktop environments need explicit MIME setup. Re-installing VS Code usually fixes it.

Status bar stuck on “connecting”

Network can’t reach the Mosayic backend.

Test connectivity: curl https://mosayic-api-service-336793731775.us-east1.run.app/health should return {"status":"ok"}.
If you’re on a corporate network, a proxy may be blocking the WebSocket upgrade. Try a different network (your phone’s hotspot is a good test).
Check the logs — you’ll see the actual error message (DNS failure, TLS error, 403, etc.).

Status bar shows “auth failed”

Your token was rejected by the backend.

Most common cause: the token was issued by a different backend than the one you’re now talking to (e.g. you switched mosayic.environment from prod to dev).
Run Mosayic: Sign Out then Mosayic: Sign In to get fresh tokens for the current backend.

Status bar shows “reconnecting”

The connection dropped and the extension is trying to re-establish it. The backoff is [1s, 2s, 5s, 10s, 30s] for up to 10 attempts.

If it’s transient (Wi-Fi blip), it’ll reconnect on its own within a minute.
If it stays in this state for 5+ minutes, the network is the problem. Check connectivity.

After 10 failed attempts, the extension stops retrying and shows “error”. Run Mosayic: Connect (or click the dashboard’s “Open VS Code” button) to retry manually.

Dashboard says “Extension not connected” but my status bar says “connected”

Two common causes:

You’re signed in with different Google accounts on the dashboard vs the extension. The dashboard refuses to send commands to an extension signed in as someone else. Sign one of them out and back in with the same account.
You signed into VS Code on a second machine. The newer connection wins, the older one was closed. Re-sign-in on the machine you want to use.

Commands aren’t running

If a dashboard click results in “command timed out”:

Check the extension’s status bar — is it actually connected?
Open the logs — do you see the command arrive? If yes, look for an error after it. If no, the WebSocket is broken.
The default consent prompt may be waiting for input behind another window. Bring VS Code to the front and look for the modal.

Docker warnings

The extension probes for Docker on activation. If you see “Docker not running” or “Docker not installed”:

Install Docker Desktop from docker.com if you don’t have it
Start Docker Desktop and wait for the menu bar icon to settle
Run Mosayic: Check Docker to re-probe

Windows: “Bash: command not found”

This usually means a command was sent through WSL Bash instead of cmd.exe.

Set mosayic.windowsShell to auto (or cmd) in your VS Code settings. The default is auto, but you may have it on gitbash from an earlier setting.

”Allow All” was a mistake

Run Mosayic: Reset Command Prompts. The extension will prompt you for every non-allowlisted command again until you choose differently.

Extension stopped working after VS Code update

Try:

Reload VS Code: Cmd/Ctrl + Shift + P → Developer: Reload Window.
Update the Mosayic extension if there’s a newer version available.
Sign out and sign back in.

If that doesn’t help, uninstalling and reinstalling the extension is safe — your auth tokens are cleared and you’ll sign in fresh.

Filing a bug

github.com/mosayic-io/vscode-mosayic/issues. Include:

The contents of your “Mosayic WebSocket” output channel (redact any private values you spot)
Your OS and VS Code version
The Mosayic extension version (Extensions panel → click the gear)
What you were trying to do and what happened instead