Editor & files
Working offline with VS Code
What keeps working in KODEO for VS Code without an internet connection, what waits, and how everything catches up when you're back online.
A linked folder: keep working
A project cloned into a folder (KODEO: Clone Project into a Folder…) is real files on your computer, so without a connection you can still:
- edit and save any file, and use every VS Code feature that doesn't need KODEO;
- run the project in VS Code's terminal —
npm run dev, tests, builds (they're yours and use no runtime hours).
When you're back online the extension catches up by itself, both ways: your saved changes are sent (all or nothing) and your teammates' are brought in with a three-way merge. If you both changed the same lines, the file gets conflict markers and the status bar counts them — fix them and save.
Straight from KODEO (kodeo://): needs the connection
A kodeo:// window has nothing on your disk. Files you already had open keep their text, but opening other files, saving and the explorer wait for the connection.
Everything live waits
Live editing, teammates' cursors, follow, comments, chat, notifications, KODEO Assist, the Trash and Source Control all talk to KODEO. While you're offline the status bar says KODEO · offline (Solo); nothing you type is lost, and a live file's edits merge back into the room when the connection returns — the same Solo mode as KODEO's web editor.
Still have a question about this?
Assist answers from this article — in any language.
Was this helpful?