Using the CLI and VS Code together

The kodeo CLI 2.0 and KODEO for VS Code 2.1 know about each other.

One sync engine per folder

A linked folder can be synced by kodeo watch or by VS Code — never both at once. Whichever starts first syncs; the other stands by and says who's syncing ("synced by kodeo watch" or "synced by KODEO for VS Code"), then takes over the moment the first one stops. Nothing is ever pushed twice.

Signing in, both ways

• VS Code from the CLI — in VS Code, choose KODEO: Sign In → Use my kodeo CLI sign-in.
• The CLI from VS Code — run kodeo login --vscode. VS Code asks you to confirm and shows the CLI's key fingerprint (the terminal shows the same one).

Either way the other gets a new sign-in of its own — never wider than the one it came from, and nothing is copied. A CLI signed in from VS Code can't use the Git remote; run kodeo login for that. Both sign-ins appear in Settings → Local access.

Notifications once

A notification popped up by the CLI (in kodeo watch, kodeo ui or on your desktop) isn't popped up again by VS Code on the same computer, and the other way round.

Open at a file and line

kodeo code src/app.ts:42
kodeo code src/app.ts:42 --cursor     # or --insiders, --windsurf, --vscodium, --web

It opens through KODEO for VS Code — the linked folder if the project is on this computer, otherwise straight from KODEO, live with your team. Which editor: the flag, then kodeo config editor, then Settings → Local access → "Open code links in", then whatever is installed. kodeo inbox open uses it for notifications that point at a line.

From VS Code

• KODEO: Open KODEO Dashboard in Terminal runs kodeo ui in a terminal tab.
• KODEO: Install or Update the kodeo CLI runs npm i -g @kodeohq/cli where you can see it.
• People using the CLI show in the Project view as "· CLI".

Keep them current

kodeo doctor shows the installed versions of both. kodeo doctor --fix installs or updates KODEO for VS Code in your editor.