Editor & files
Work locally with the kodeo CLI
Clone a KODEO project into a folder on your computer, edit it in any editor, and pull and push — or keep it in sync with kodeo watch.
The kodeo command-line tool puts a KODEO project in a real folder on your computer. Every change still goes through the same rules as the editor — roles, plan limits, version checks and the trash.
Install and sign in
npm i -g @kodeohq/cli
kodeo loginkodeo login opens KODEO in your browser; you choose what the CLI may do and approve. On a machine without a browser (SSH, a container), use kodeo login --device and enter the code it shows at kodeo.website/device. Needs Node 20 or newer.
Clone, pull, push
kodeo clone acme/storefront
cd storefront
kodeo status
kodeo pull
kodeo push- pull downloads only what changed. A file changed both here and on KODEO is merged; if the same lines changed, conflict markers are written.
- push sends your changes as one all-or-nothing transaction. If a file you're pushing changed on KODEO since your last pull, nothing lands and you're told who changed it — run
kodeo pull, then push again. - Deleted files go to KODEO's trash for 7 days (
kodeo trash). - Every write command takes
--dry-run.
Keep it in sync
kodeo watch pushes each save and pulls teammates' changes within a second. In the editor you appear as syncing from a local folder. If a file conflicts, watch writes markers and pauses just that file until you resolve it.
Running code locally
It's a normal folder, so npm run dev, tests and builds work in any terminal. That run stays on your machine: teammates see your code (every push), not its output, and it uses no runtime hours.
What never syncs
node_modules, .git, .kodeo/local (the CLI's own state) and OS files. kodeo clone writes a starter .kodeoignore for your framework; it uses the same syntax as .gitignore.
Still have a question about this?
Assist answers from this article — in any language.
Was this helpful?