Troubleshooting
KODEO for VS Code troubleshooting
Fixes for the extension — Open in VS Code does nothing, the sign-in doesn't come back, "offline (Solo)", read-only, conflicts, and vscode.dev.
"Open in VS Code" does nothing
The link only works where KODEO for VS Code is installed. After a moment KODEO says so and offers the Marketplace (VS Code) and Open VSX (Cursor, Windsurf, VSCodium). Install it, then try again. Your browser may ask "Open Visual Studio Code?" the first time — allow it.
The sign-in never comes back to VS Code
- Make sure you approved in the browser, and that the browser was allowed to open VS Code.
- The code lives for one minute. If it expired, run KODEO: Sign In again.
- On a machine where the browser can't reach VS Code (a remote server), use KODEO: Sign In with a Code.
The status bar says "offline (Solo)"
The live connection isn't available — your network, a proxy that blocks WebSockets, or KODEO's live service being paused. Nothing is lost: saves are version-checked, exactly like the web editor's Solo mode, and your edits merge back when the connection returns. KODEO: Refresh retries.
"read-only"
You're a Viewer in that workspace, your sign-in is read-only, or the room is full and you're a spectator (you're promoted when a seat frees). In a linked folder, VS Code's Restricted Mode (an untrusted folder) also keeps KODEO read-only — trust the folder to edit live.
"Signed out — …"
KODEO ended the sign-in and says why: a password change, "This wasn't me", a workspace policy, or it was signed out in Settings → Local access. Choose Sign In Again.
Conflict markers in a linked folder
A file that wasn't open changed on KODEO while you changed it too. Edit the <<<<<<< / >>>>>>> blocks, keep what you want, and save — the status bar count drops and the file is sent. Binary files never get markers: KODEO's copy is saved beside yours as name.kodeo.ext.
Search or Ctrl+P finds nothing in a kodeo:// window
VS Code's own search can't look inside a kodeo:// project. Use KODEO: Search in Project… and KODEO: Go to File… — in a kodeo:// window Ctrl+Shift+F and Ctrl+P already do.
vscode.dev says it can't make a key
KODEO needs Ed25519 in the browser's Web Crypto to bind your sign-in to it. Use a current Chrome, Edge, Firefox or Safari — or desktop VS Code.
Where are the logs?
View → Output → KODEO. It never contains tokens or file contents. KODEO: Ask Assist opens KODEO Assist in your browser, told which editor you're in and whether you're live — never your code.
Still have a question about this?
Assist answers from this article — in any language.
Was this helpful?