KODEO for VS Code

KODEO for VS Code makes VS Code a full KODEO client. Open a project and you're in the room: your teammates in the browser see your cursor as you type, and you see theirs. Nothing changes for anyone who doesn't use it.

Install it

• VS Code and VS Code Insiders: Extensions view (Ctrl+Shift+X / ⌘⇧X) → search KODEO → publisher kodeohq → Install.
• Cursor, Windsurf and VSCodium: the same search — they install from Open VSX.
• vscode.dev and github.dev: the same search in the browser's Extensions view.

The extension's id is kodeohq.kodeo. It does nothing until you open a KODEO project or run one of its commands, so installing it costs an unrelated folder nothing.

Sign in

Run KODEO: Sign In from the Command Palette (or choose KODEO in VS Code's Accounts menu) and approve on kodeo.website — with your passkey or two-factor, as usual.

• The sign-in code comes back through the extension's own link, works once, lives for a minute, and is useless without a secret only that window holds.
• The sign-in is bound to an Ed25519 key only this editor has. Every refresh is signed with it, so a copied token doesn't work anywhere else.
• It's kept in VS Code's secret storage (your operating system's keychain on desktop), never in settings or the workspace.
• It appears under Settings → Local access → Signed-in computers, labelled VS Code with its version. Sign it out there, or with KODEO: Sign Out.

No browser on that machine (a remote server, a locked-down laptop)? Use KODEO: Sign In with a Code and approve the code at kodeo.website/device. Already signed in with the kodeo CLI on the same computer? KODEO: Use My kodeo CLI Sign-In asks KODEO for a new VS Code sign-in — nothing is copied from the CLI.

Open a project

• KODEO: Open Project… lists every project you can reach. You can also paste a reference like acme/storefront:src/app.ts:42.
• Open in VS Code in KODEO's web editor (the top bar, or the chevron beside it) opens the file you're on, at your line.
• kodeo open src/app.ts:42 --vscode does the same from a terminal.

A project opens either straight from KODEO (a kodeo:// window — nothing to download, works on vscode.dev) or as a linked folder on your computer. See Linked folders or kodeo://? for the difference.

In the room

• Cursors — teammates' cursors and selections in their colours, with their names. The Room view shows who's here, in which file, and whether they're in a browser or in VS Code. Someone in both counts once.
• Follow — click a teammate in the Room view to follow their file, cursor and scrolling. Typing, scrolling or Esc stops it.
• Bring Everyone Here — sends the room to your line (with an optional note). Summons from the browser arrive in VS Code too.
• Comments — the same threads as the browser, in VS Code's comment UI, pinned to the right line even after edits above them.
• Chat and notifications — in the KODEO sidebar.
• Undo is yours — Ctrl+Z / ⌘Z in a live file undoes your own edits, never a teammate's.
• Checkpoints — KODEO: Create Checkpoint and KODEO: Checkpoints…, the same history as the web editor.

The status bar says where you stand: KODEO · live · 3 here, KODEO · 2 to push, KODEO · 1 conflict, KODEO · offline (Solo) or KODEO · read-only. Click it for everything you can do.

If the live connection drops

KODEO switches to Solo mode, exactly like the web editor: saves are version-checked, and nothing you type is lost. When the connection comes back, your edits merge into the room.

Roles and policies

• A Viewer gets a read-only project in VS Code; the server refuses their edits whatever the editor does.
• Over your plan's editing limit, you join as a spectator and are promoted when a seat frees — the same as the browser.
• A Team can turn the extension off under Workspace settings → Local access. Doing so ends VS Code sign-ins that reach only that workspace and closes VS Code's live connections there at once.

Running code

KODEO's Run stays in the browser — it's the shared, metered runtime your teammates can watch. KODEO: Run in KODEO opens it there. In a linked folder, npm run dev, tests and builds in VS Code's terminal are yours: private, and they use no runtime hours.