KODEO for VS Code troubleshooting

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

"This link can't sign anything in"

KODEO refused the address the sign-in asked to return to — the page shows it ("Asked to return to …"). Extension versions 1.1.0 and 1.1.1 sent it in a shape VS Code had re-encoded; update the extension (Extensions view → KODEO → Update) and choose KODEO: Sign In again. KODEO: Sign In with a Code always works in the meantime.

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.

Where did Chat and Assist go?

Since 2.0 they're in the KODEO panel, next to the terminal, with Help and Support. Alt+J opens the chat and Alt+A Assist. Drag the panel's KODEO tab to the Secondary Side Bar to keep it beside your code.

"Failed to save … The content of the file is newer"

Versions before 2.0 could show this when saving a file that was live in the room (the room saves live files every few seconds, which looked to VS Code like someone else's save). Update the extension. Since 2.0 a live file's saves always go through, and a real conflict on a file that isn't live is shown as KODEO's own choice — Compare, Keep Mine or Use KODEO's — never VS Code's raw error.

Notifications don't pop up

See Notifications in VS Code — usually KODEO › Notifications: Pop-ups is off, pop-ups are paused, the project is muted, or the type's Push is off in Settings → Notifications. They're still listed in Activity.

"Webview is disposed"

Versions before 2.0 could show this when opening Assist a second time after closing its tab. Update the extension — 2.0 never touches a closed view.

The status bar says Solo or reconnecting

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.

A teammate's change doesn't show up

Files created, renamed, deleted or typed into in the browser arrive by themselves within a second or two. If one doesn't:

• Check the status bar shows the project as live — in Solo mode, changes arrive when the connection returns.
• Choose KODEO: Refresh (reloads the file list, Git and notifications).
• In a linked folder, choose KODEO: Sync Linked Folder Now.
• Make sure the extension is up to date: versions before 1.1.2 missed some browser changes.

"… changed on KODEO while you were editing it"

You saved a file that isn't live while a teammate saved a newer version. Nothing is overwritten until you choose: Compare (both texts side by side), Keep Mine (yours replaces theirs) or Use KODEO's (their text replaces yours). Files that are live in the room never conflict — the room merges every keystroke.

Following someone stops by itself

Typing, clicking into another file, scrolling yourself or Esc stops following — by design. If the person closes KODEO, following waits half a minute (a reload, a slow connection) before it stops.

Start fresh

KODEO: Reset KODEO on This Computer… signs out and forgets what KODEO keeps on this computer (cached files, recent projects, the Help index, pop-up choices, offline saves — it says how many first). Your settings and your projects on KODEO are untouched. Sign in again afterwards.

Where are the logs?

View → Output → KODEO. It never contains tokens or file contents. KODEO: Ask Assist opens KODEO Assist right in VS Code — it's told which editor you're in and whether you're live, never your code. Still stuck? KODEO: New Support Ticket… reaches a person.

"Synced by kodeo watch — VS Code stands by"

The kodeo CLI is already syncing this linked folder (kodeo watch, or kodeo ui --watch), so VS Code doesn't push or pull too — one sync engine per folder. Stop it in the terminal (Ctrl+C) and VS Code takes over within a few seconds.