KODEO for VS Code 2.0

Your editor.Their browser.One room.

Open a KODEO project in VS Code and work live with your team — their cursors, comments, chat and Assist, notifications from anywhere, shared terminals, pull request reviews and the project’s Git, where you already work.

KODEO · publisher kodeohq
Install for VS CodeCursor, Windsurf, VSCodium

Free on every plan. Create a free account →

New in 2.0

Everything you do,without switching windows.

One panel for chat, Assist, Help and Support

The room’s chat, KODEO Assist with past conversations, the whole Help Center searched as you type, and your tickets — four tabs in VS Code’s Panel, or beside your code.

Notifications, everywhere

They reach VS Code with no project open. A mention opens the comment thread itself; your settings, pause and quiet hours decide what pops up — once, in the window you’re using.

Teammates’ terminals

Watch a terminal a teammate shares from the browser, live in a VS Code terminal. Press Enter to ask for the keyboard.

Pull request reviews

Every changed file, comments on lines, Approve or Request changes, merge, check out — without leaving VS Code.

The commit graph

Every branch drawn as lanes. Click a commit for its files and diffs; toggle blame for the whole file, shaded by age.

Conflicts, resolved

VS Code’s 3-way merge editor for KODEO merges — or Accept Current, Incoming or Both above each conflict.

Who’s where

Files teammates have open carry their initials in the explorer and on tabs. See who follows you — and ask them to stop.

Never lose a save

A ✓ when the room has every edit. Offline, saves wait on your computer and go out — version-checked — when you’re back.

Sixty seconds

Install, sign in,you’re in the room.

  1. Install

    Extensions (Ctrl+Shift+X) → search KODEO → publisher kodeohq → Install. In Cursor, Windsurf and VSCodium it comes from Open VSX.

    ext install kodeohq.kodeo

  2. Sign in

    KODEO: Sign In, then approve in your browser with your passkey or two-factor. No browser? Sign In with a Code.

    KODEO: Sign In

  3. Open a project

    Alt+K: your recent projects and every one you can reach — straight from KODEO, or a folder that stays in sync.

    KODEO: Switch Project…

The side bar, redesigned

Four views,room for each.

KODEO

1 PROJECT

storefront Live · 3 here

AS Asha refund.ts · typing

RV Ravi following you

Plan & usage Pro · 62% storage

2 COMMENTS Open

refund.ts 2

3 ACTIVITY 1 new

Asha mentioned you now

4 PROJECT TOOLS

Terminals 1 shared

Checkpoints · Trash · Sign-ins

  1. Project

    Live or Solo, who’s here and in which editor, who’s typing, who’s following you, who’s running the project and on which port — and your plan’s storage and runtime hours.

  2. Comments

    Every thread in the project, grouped by file: open, resolved, yours, or where you’re mentioned. A click opens the thread at its line.

  3. Activity

    Your notifications by day — mark read, open in the browser, mute a project’s pop-ups.

  4. Project Tools

    Shared terminals, the file’s checkpoints (compare, then restore), the trash, and your sign-ins — each loaded only when you open it.

Two ways to open a project

On your disk,or not at all.

Straight from KODEO

Nothing to download

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.

  • One request for the whole file tree
  • Saves are version-checked — offline ones too
  • KODEO Search and Go to File built in

A linked folder

Real files, kept in sync

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.

  • The same folder kodeo clone makes
  • Three-way merges, conflicts marked
  • Local runs use no runtime hours

In the room

Everything thebrowser has.

Live editing

Character by character with teammates in the browser or in VS Code — one CRDT underneath, so nobody overwrites anybody, even on the same line.

Both directions

Files a teammate creates, renames, deletes or types into in the browser appear in VS Code by themselves — and yours in theirs.

Cursors & follow mode

Everyone’s cursor in their colour. Follow someone’s file, cursor and scrolling; Esc stops. Someone following you? The status bar says so.

Bring everyone here

Send the room to your line with a note — and answer the browser’s summons from VS Code.

Comments with @mentions

The same threads as the browser in VS Code’s Comments UI (Alt+C). @ suggests teammates — the person you mention is notified.

KODEO Assist

Ask anything about KODEO without leaving the editor — answers stream in with their Help articles, and past conversations resume. It never sees your code.

The Help Center

Every article, searched instantly as you type (nothing is sent while you type), opened right in the panel.

Support tickets

Open a ticket, follow the replies, mark it solved, rate the help — a reply from the KODEO team pops up in VS Code.

Checkpoints & trash

Compare a checkpoint with the file now before restoring it; bring back anything deleted in the last 7 days — for everyone.

Undo that’s yours

Ctrl+Z undoes your own edits — never a teammate’s — exactly like the web editor.

Never load-bearing

Connection gone? Solo mode: version-checked saves, nothing lost, and your edits merge back when it returns.

Switch & start projects

Alt+K switches between projects (recent first); New Project… starts one from a template. Open in VS Code works from the browser and your phone.

Notifications

From your phoneto your editor.

  1. On your phone

    Send to my computer from the mobile editor — or a teammate mentions you, asks for your review, or replies to your ticket.

  2. In VS Code, at once

    Over KODEO’s live channel — no project needs to be open. It pops up once, in the window you’re using; everything waits in Activity.

  3. Right where it points

    The file and line, the comment thread itself, the chat, a pull request, a ticket or a Help article.

Your rules: types with Push on pop up (security notices always); KODEO’s pause and quiet hours apply. Change them in the Help Center.

Source Control

The project’s Git,all of it.

SOURCE CONTROL main · 2↑
Refunds land in the ledger — main is protected
✓ Commit to refunds

Your Staged Changes

refund.ts M

Changes — Priya has 2 staged

ledger.ts A

KODEO History

Add refunds Priya · 2 h

Cart totals You · 1 d

if (!paid) returnAsha, 2 hours ago • Guard empty orders

  • Start, bring one in, publish

    Initialize Repository for the whole project, clone any public GitHub repository by link, link one, or Publish to GitHub — and connect GitHub right from VS Code: approve on GitHub and it carries on by itself.

  • Per-person staging

    What you stage is yours; teammates’ staging shows as a note. Commit with co-authors from the room — live files are settled first.

  • Graph, history & blame

    Every branch in the commit graph, KODEO History in Source Control, a file’s history — and blame for the line or the whole file.

  • Branches, GitHub’s too

    Switch (for everyone, your changes parked), create, rename, delete — and check out a GitHub branch as a local one. Fetch a shallow clone’s full history.

  • Reviews and merges

    Review pull requests in VS Code — line comments, approve, request changes, merge. Resolve conflicts in the 3-way merge editor.

  • Rules, said first

    A protected default branch or required pull requests are shown before a push is refused — with the branch-and-PR way that works.

Keyboard

The shortcutsyou already know.

  • AltKSwitch project
  • AltJChat
  • AltAAsk Assist
  • AltCComment on this line
  • Ctrl⇧JPeople
  • AltGSource Control
  • CtrlPGo to file (kodeo://)
  • Ctrl⇧FSearch the project
  • CtrlZUndo — only yours
  • EscStop following
  • Alt/Every KODEO shortcut

Only in KODEO windows (or once you’re signed in) — the rest of VS Code keeps its own keys. On a Mac, Ctrl is ⌘ and Alt is ⌥.

Every command

83 commands,one palette.

Sign in

KODEO: Sign In
Approve in your browser (passkey or two-factor as usual). The code comes back through the extension’s own link and works once.
KODEO: Sign In with a Code
For machines without a browser: approve a short code at kodeo.website/device.
KODEO: Use My kodeo CLI Sign-In
A new VS Code sign-in from your signed-in kodeo CLI — nothing is copied. Desktop only.
KODEO: Sign Out
Ends this editor’s sign-in on KODEO too.
KODEO: Manage Sign-ins and Tokens
Your computers signed in to the CLI, VS Code or Git, and your tokens, in Settings → Local access. Project Tools → Sign-ins signs one out from VS Code.

Projects

KODEO: Switch Project…Alt+K
Recent projects first, then every project you can reach, by workspace — the button on a row opens it in a new window.
KODEO: Open Project…
Pick a project (or paste acme/storefront:src/app.ts:42): your linked folder if this computer has one, otherwise straight from KODEO.
KODEO: New Project…
A workspace, a name and a template — KODEO writes the starter files, then it opens here.
KODEO: Clone Project into a Folder…
Real files that stay in sync — the same folder `kodeo clone` makes. Desktop only.
KODEO: Sync Linked Folder Now
Pull teammates’ changes and send yours, right now.
KODEO: Send Offline Saves Now
Saves made while offline wait on this computer and go out by themselves when KODEO is back — this tries at once (version-checked, never over a teammate’s newer save).
KODEO: Go to File…Ctrl+P (kodeo://)
Every file in the project, with who has it open — also ⌘P / Ctrl+P in a kodeo:// window.
KODEO: Search in Project…Ctrl+Shift+F (kodeo://)
KODEO’s own project search, results opening at the line — also ⌘⇧F / Ctrl+Shift+F in a kodeo:// window.
KODEO: Open in Browser
This file and line in KODEO’s web editor.
KODEO: Copy Link to This Line
A link teammates can open in the browser or VS Code.
KODEO: Create Checkpoint
A named checkpoint of this file — the same history as the web editor.
KODEO: Checkpoints…
Pick one to compare with the file now, and restore it from there (for everyone, undoable).
KODEO Trash: Empty Trash
Project Tools → Trash lists deleted files for 7 days — Restore brings one back for everyone; this empties it for good.
KODEO: Run in KODEO
Opens the project’s Run panel in the browser — the shared runtime teammates can watch.
KODEO: Open Billing
The workspace’s plan, storage and runtime hours (Project → Plan & usage shows them here).

In the room

KODEO: Follow a Teammate…
Follow their file, cursor and scrolling. Typing, scrolling or Esc stops.
KODEO: Stop FollowingEsc
Stop following.
KODEO: Stop Everyone Following Me
Anyone following you stops (in the browser too), and nobody can follow you for a minute.
KODEO: Bring Everyone Here
Send the room to your line, with a note.
KODEO: Watch a Teammate’s Terminal…
A terminal a teammate shares from the browser, live in a VS Code terminal — read-only; press Enter in it to ask for the keyboard.
KODEO: Comment on This LineAlt+C
Start a comment thread on the line — teammates see it in the browser at once; @ suggests people to mention.
KODEO: Suggest a Change to These Lines
A comment that proposes new text for the selected lines: paste the ```suggestion block it copies, edit it, and post. Anyone who can edit applies it with one click — Apply Suggestion on the thread here, or Apply in the browser.
KODEO: Filter Comments…
The Comments view: open threads, resolved ones, yours, or where you’re mentioned.
KODEO: Share Port with KODEO…
Desktop: an app running on this computer gets its own link on KODEO’s preview domain — teammates, signed-in people, anyone, a password or a webhook URL. Loopback only; requests are logged to the “KODEO Preview” output. The Previews view lists everything shared in the project — open a teammate’s running app in your browser or beside your code.
KODEO: Shared Ports…
The ports you’re sharing from this computer: copy a link, open it, see who’s watching, stop.
KODEO: Open Preview in VS Code
A live app — yours or a teammate’s — in a VS Code tab: pick the app, reload, phone / tablet / laptop sizes, who’s watching (and from where), copy the link, open in your browser. The Previews view lists the project’s live apps, one per person and port; click one to watch it here.
KODEO: Show PeopleCtrl+Shift+J / ⌘⇧J
Who’s here (and in which editor), who’s following whom, who’s running the project.
KODEO: Keyboard ShortcutsAlt+/
Every KODEO shortcut in one list — pick one to run it, or change the keys.
KODEO: Undo My Last EditCtrl+Z / ⌘Z
Undo in a live file — only your own edits, never a teammate’s.
KODEO: Redo My Last EditCtrl+Shift+Z / ⌘⇧Z
Redo your own edit.
KODEO: Show KODEO Menu
Everything you can do from here, grouped (also the status bar item).
KODEO: Open KODEO Dashboard in Terminal
Runs `kodeo ui` — the kodeo CLI’s full-screen dashboard — in a terminal tab, for this linked folder or the open project. Needs the CLI (2.0+).
KODEO: Install or Update the kodeo CLI
Runs `npm i -g @kodeohq/cli` in a terminal you can see.
KODEO: Refresh
Reload the project’s files, Git state, comments, usage and notifications.

Chat, Assist, Help and Support

KODEO: Open ChatAlt+J
The room’s chat, in the KODEO panel — @ suggests teammates.
KODEO: Open Chat in an Editor Tab
The chat as an editor tab — as wide as you like.
KODEO: Ask AssistAlt+A
KODEO Assist in the KODEO panel — answers stream in, with the Help articles they come from, and past conversations to resume. It’s told which editor you’re in and whether you’re live — never your code.
KODEO: Search Help…
The whole Help Center, searched instantly as you type; articles open in the panel.
KODEO: Support Tickets
Your tickets: follow the replies, mark one solved, rate the help.
KODEO: New Support Ticket…
A person from KODEO replies. VS Code attaches its state (editor, live or not, version) — never code.

Notifications

KODEO: Mark All as Read
Your KODEO notifications (the Activity view), all read.
KODEO: Notification Pop-ups…
Which notifications pop up in VS Code (important · everything · off), pause them for an hour, unmute a project — or open your KODEO notification settings.

Source Control (the project’s Git)

KODEO Git: Commit
Commit your staged changes — with co-authors from the room. Live files are settled first, so the commit holds what’s on screen.
KODEO Git: Commit & Push
Commit, then push to GitHub (on KODEO’s server).
KODEO Git: Commit (Amend)
Amend the last commit — refused once it’s pushed.
KODEO Git: Stage All Changes
Your staging is yours — teammates stage their own.
KODEO Git: Unstage All Changes
Unstage everything you staged.
KODEO Git: Switch Branch…
Your branches and GitHub’s (checked out as a local branch) — switches the project for everyone; your uncommitted changes are parked and come back.
KODEO Git: Create Branch…
A new branch, optionally switching to it.
KODEO Git: Pull
From GitHub, merged on KODEO’s server.
KODEO Git: Push
To GitHub — your GitHub token never reaches VS Code. A protected branch says so before anything is refused.
KODEO Git: Fetch
What’s new on GitHub.
KODEO Git: Fetch the Full History
A shallow clone’s whole history, on demand.
KODEO Git: Show Branch Rules
This workspace’s rules for the default branch: protected (admins only) and pull requests required.
KODEO Git: Publish to GitHub…
Create a GitHub repository for this project.
KODEO Git: Initialize Repository
Start Git for this project (for everyone in it), with an optional .gitignore.
KODEO Git: Clone from GitHub…
Any public repository by link, or one of yours — its files become the project’s (the old ones go to the trash).
KODEO Git: Link a GitHub Repository…
Point pushes and pulls at an existing GitHub repository.
KODEO Git: Unlink GitHub Repository
Stop syncing with GitHub; the history stays.
KODEO Git: Merge Branch…
Merge another branch into the current one — conflicts show up in Source Control and in the files.
KODEO Git: Open in Merge Editor
Resolve a conflicted file in VS Code’s 3-way merge editor (or with Accept Current / Incoming / Both above each conflict).
KODEO Git: Abort Merge
Put the files back as they were before the merge.
KODEO Git: Rename Branch…
Rename a branch.
KODEO Git: Delete Branch…
Delete a branch (asks before dropping unmerged work).
KODEO Git: Stash Changes…
Put your changes aside; Pop / Apply / Drop Stash… bring them back or discard them.
KODEO Git: Pop Stash…
Apply a stash and drop it.
KODEO Git: Apply Stash…
Apply a stash and keep it.
KODEO Git: Drop Stash…
Delete a stash for good.
KODEO Git: Create Tag…
Tag the current commit (a message makes it annotated). Right-click a commit in KODEO History to tag that one.
KODEO Git: Delete Tag…
Delete a tag on KODEO.
KODEO Git: File History
The commits that changed this file, in KODEO History (Source Control) — each opens as a diff; right-click to restore that version.
KODEO Git: Show Commit Graph
Every branch drawn as lanes, in an editor tab — click a commit for its files and diffs, right-click for branch, tag, copy and GitHub.
KODEO Git: Toggle File Blame
Who changed every line of this file, and when — shaded by age.
KODEO Git: Refresh
Reload the repository state.
KODEO Git: Create Pull Request…
From the current branch to the default one.
KODEO Git: Refresh
Reload pull requests and CI checks. Click a pull request to review it in VS Code: files, line comments, approve or request changes, merge, check out.

This computer

KODEO: What’s New
The walkthrough: what KODEO for VS Code does, step by step.
KODEO: Reset KODEO on This Computer…
Sign out and forget what KODEO keeps here — cached files, recent projects, the Help index, pop-up choices, offline saves (it says how many first). Settings and projects are untouched.

Settings

kodeo.server
The KODEO server (https only; http://localhost for development). Default https://www.kodeo.website. Not synced between computers.
kodeo.notifications.popups
Which KODEO notifications pop up in VS Code: important (default — Push-on types, mentions, replies, reviews, support replies, anything sent to this computer) · all · off. KODEO’s pause and quiet hours apply.
kodeo.presence.showNames
Show teammates’ names next to their cursors (initials once they’re still); hover a cursor for who, where and what. Left unset (2.2+), it follows your KODEO editor setting — always, while typing, or on hover only; on or off here overrides it.
kodeo.presence.explorerBadges
Badge files teammates have open — explorer, tabs, Go to File — with their initials. Default on.
kodeo.roomMessages
Pop up teammates’ comments, replies, chat messages and someone starting to follow you. Default on.
kodeo.git.inlineBlame
Who last changed the line your cursor is on, at the end of the line. Default on.
kodeo.linkedFolder.syncOnSave
In a linked folder, send saved files to KODEO right away. Default on.
kodeo.openLinksIn
Where Open in VS Code links open a project: linked (default) · remote · ask. Per computer.
kodeo.accessibility.announce
Announce who joins or leaves the room, and the room going offline or back: auto (default — with VS Code’s screen-reader mode) · always · never.
kodeo.telemetry.sharePerformance
Send a few anonymous speed numbers (activation, opening a project, joining the room, edit round trips). Off by default, and never while VS Code’s telemetry is off.

Safe by design

A sign-inis a session.

How KODEO protects you

Everywhere you code

One extension,nine places.

  • VS Code
  • VS Code Insiders
  • Cursor
  • Windsurf
  • VSCodium
  • vscode.dev
  • github.dev
  • GitHub Codespaces
  • Remote SSH & WSL

83 commands in the Command Palette — every one of them, and the Help Center guide.

Questions

Asked, andanswered plainly.

What’s new in 2.0?
Chat, Assist, Help and Support in one panel; notifications that reach VS Code with no project open (and open the comment itself); teammates’ shared terminals; pull request reviews; the commit graph and whole-file blame; the merge editor; presence badges on files; a sync ✓; offline saves; project switching and creation; a redesigned side bar.
Do my teammates need the extension?
No. They keep working in the browser; you show up in the same room with a “VS Code” badge. Uninstalling it changes nothing for anyone else.
Where did Chat and Assist go?
Into the KODEO panel, beside the terminal — with Help and Support. Drag its tab to the Secondary Side Bar to keep it next to your code, or open any tab as an editor tab.
Which notifications pop up?
The types whose Push is on in your KODEO notification settings, plus mentions, replies, summons, review requests, support replies and anything you send to this computer. KODEO’s pause and quiet hours apply; you can also pause pop-ups in VS Code, mute a project, or choose “everything” or “off”.
Can I run my project?
In a linked folder, yes — npm run dev, tests and builds in VS Code’s terminal are yours: private, and they use no runtime hours. KODEO’s shared Run stays in the browser; the status bar shows who’s running it, and you can watch a shared terminal from VS Code.
Does it work in Cursor and Windsurf?
Yes. They install extensions from Open VSX, where KODEO is published too (publisher kodeohq). So are VSCodium and — in the browser — vscode.dev and github.dev.
What if I’m offline?
Live files keep your edits and send them when the connection is back. A file opened straight from KODEO saves on your computer and goes to KODEO later — version-checked, so a teammate’s newer save is never overwritten. A linked folder works fully offline.
Does KODEO Assist read my code?
No. Assist in VS Code is told which editor you’re in, whether you’re live and your role — state words only, checked on the server. With your OK it can read your plan and settings; never files, errors or terminal output.
Does the extension send data about me?
Only what you use it for. Speed numbers (activation, joining the room, edit round trips) are off unless you turn them on — and never while VS Code’s own telemetry is off. They carry no name, project or file.
How do I sign out — or start fresh?
KODEO: Sign Out, or end it in KODEO under Settings → Local access. KODEO: Reset KODEO on This Computer… also forgets cached files, recent projects and pop-up choices.

Ready whenyou are.

A workspace, a project and a live editor in under a minute. Free, no card.

Start building free
The CLI and Git