KODEO for VS Code
Open a KODEO project in VS Code — straight from KODEO, or in a folder that stays in sync — and edit it live with your team. Their cursors, comments, chat and the project’s Git, where you already work.
KODEO · publisher kodeohqFree on every plan. Create a free account →
1export async function checkout(cart) {
2 const total = sum(cart.items)
3 if (!total) return null
4 return pay(total, cart.currency)
5}
6// Ben: handle refunds here
1export async function checkout(cart) {
2 const total = sum(cart.items)
3 if (!total) return null
4 return pay(total, cart.currency)
5}
6// Ben: handle refunds here
Sixty seconds
Extensions (Ctrl+Shift+X) → search KODEO → publisher kodeohq → Install. In Cursor, Windsurf and VSCodium it comes from Open VSX.
ext install kodeohq.kodeoKODEO: Sign In, then approve in your browser with your passkey or two-factor. No browser? Sign In with a Code.
KODEO: Sign InStraight from KODEO (nothing to download), or clone it into a folder that stays in sync.
KODEO: Open Project…Two ways to open a project
Straight from KODEO
Open kodeo://acme/storefront and start typing. Files arrive as you open them and are cached by content — even on vscode.dev and github.dev.
A linked folder
Clone into a folder: files you have open are live, everything else is sent when you save — all or nothing. Your terminal, tests and dev server run privately.
In the room
Character by character with teammates in the browser or in VS Code — one CRDT underneath, so nobody overwrites anybody, even typing on the same line.
Files a teammate creates, renames, deletes or types into in the browser appear in VS Code by themselves — and yours in theirs.
Everyone’s cursor in their colour; hover one for who, where and whether they’re typing. Follow someone’s file, cursor and scrolling; Esc stops.
Send the room to your line with a note — and answer the browser’s summons from VS Code.
The same threads as the browser in VS Code’s Comments UI (Alt+C on a line); chat in the sidebar or a full tab. Teammates’ messages pop up.
Ask anything about KODEO without leaving the editor — answers stream in with the Help articles they come from. It never sees your code.
Your KODEO notifications in the sidebar. Send a file from your phone and it pops up the moment you’re back in VS Code.
Named checkpoints you can restore, and a Trash view with everything deleted in the last 7 days — for everyone in the project.
Ctrl+Z undoes your own edits — never a teammate’s — exactly like the web editor.
Connection gone? Solo mode: version-checked saves, nothing lost, and your edits merge back when it returns.
From the web editor, a notification or Assist — or kodeo open --vscode. On a phone: send it to your computer.
KODEO’s own project search and Go to File — Ctrl+Shift+F and Ctrl+P in a kodeo:// window, where VS Code’s can’t reach.
Source Control
Your Staged Changes
checkout.ts M
Changes — Priya has 2 staged
README.md M
refunds.ts A
KODEO History
Add refunds Priya · 2 h
Cart totals You · 1 d
if (!total) return nullPriya Shah, 2 hours ago • Guard empty carts
Initialize Repository for the whole project, clone any public GitHub repository by link, or link an existing one.
What you stage is yours; teammates’ staging shows as a note. Commit with co-authors from the room — live files are settled first.
KODEO History in Source Control — commits, their files and diffs, one file’s history — and who changed the line you’re on.
Switch (for everyone, your changes parked), create, rename, delete; merge with conflicts in the files; stash, pop, tag.
Push, pull, publish, pull requests and CI checks — run by KODEO with your GitHub connection. The token never reaches VS Code.
The secret scan and sensitive paths ask first; discarded work goes to the trash; restore any file to any commit.
Keyboard
Only in KODEO windows — the rest of VS Code keeps its own keys. On a Mac, Ctrl is ⌘.
Every command
kodeo.serverkodeo.presence.showNameskodeo.roomMessageskodeo.git.inlineBlamekodeo.linkedFolder.syncOnSavekodeo.openLinksInSafe by design
A sign-in only this editor can use
Approved in your browser with your passkey or two-factor; the code returns through the extension’s own link and works once. Every refresh is signed by an Ed25519 key only this editor holds.Kept in the keychain
Tokens live in VS Code’s secret storage — the OS keychain on desktop — never in settings, the workspace or a log. GitHub tokens never reach VS Code at all.The same rules as the browser
Viewers get a read-only project and the server drops their edits; a full room makes you a spectator; a Team can switch the extension off.Untrusted stays read-only
In a folder you haven’t trusted, nothing is sent until you trust it. Chat, comments and notifications are shown as text, never HTML.Everywhere you code
57 commands in the Command Palette — every one of them, and the Help Center guide.
Questions
A workspace, a project and a live editor in under a minute. Free, no card.