Run & terminal
Run your project
How Run works in your own browser, which browsers support it, the Preview, dependency caching and run settings.
How it works
Run starts your project inside your own browser tab — Node.js runs there in WebAssembly. Nothing runs on KODEO's servers, which is why it's fast to start and why it depends on your browser.
- Press Run (or Alt + R). The first run installs dependencies; they're cached in this browser, so the next run is much faster.
- When your app opens a port, the Preview shows it and reloads as you type.
- Stop ends the command; the runtime stays ready for the next run until you close the tab or leave it idle.
Which browsers
| Device | Run |
|---|---|
| Chrome, Edge, Brave, Opera, Firefox or Safari 16.4+ on a laptop or desktop | Yes |
| iPhone or iPad (any browser) | No — iOS browsers can't host the runtime. Editing, chat, comments and Git all work. |
| Android phones | Often, but they're low on memory for installs |
Run needs the editor page to load "isolated". If it says the runtime needs a fresh load of this page, just reload.
Run settings
Run settings (in the Run menu) sets the start command, the port, and environment variables, saved in .kodeo/environment.json. KODEO guesses the command from package.json scripts.
Problems
Errors from the build, the runtime and your running page are gathered in the Problems list, and underlined in the editor.
Limits
Runtime hours are counted while a runtime is running — see Runtime hours. Each plan allows a number of runtimes at once across the workspace (Free 1, Pro 3, Team 2 per seat), and a runtime nobody's looking at stops after a while.
Still have a question about this?
Assist answers from this article — in any language.
Was this helpful?