Edit code in your browser with Code-Server

Run a full VS Code in a browser tab, hosted on your own Falix server — the Code-Server application, how to open it, sign in, and where it fits.

Code-Server is VS Code running in a browser tab, hosted on a Falix server of its own. You get the real editor — file tree, extensions, integrated terminal, find-and-replace — reachable from any machine with a browser, nothing to install. It's an application you create like any other, with one catch: it's available at creation on premium plans only (it isn't in the free allow-list).

At a glance
Plan Premium — Code-Server isn't in the free allow-list
Time About ten minutes to have the editor open

Create it

On the Create server page, open the Applications catalog and pick Code-Server — VS Code in Browser. Create the server and let it install — it downloads and sets up code-server for you. When it's done, start it like any server.

Open it and sign in

Code-Server listens on your server's public port, so you open it in a browser at http://address:port — the exact address and port are on the server's Network page. It loads to a sign-in screen.

The password is generated for you at install. Open Settings → Environment and look at the Password variable — that's your login. You can change it there whenever you like: edit the variable, then restart the server so the new value takes effect.

⚠️ Heads up: Anyone with the password and the address can reach your editor, so pick a strong one if the port is exposed to the world.

Once you're in, it behaves like the VS Code you already know — open a folder, install the extensions you want, split the editor, use the integrated terminal. Anything you save lives in this server's files, so it's there next time you sign in.

🎯 Good to know: Do my extensions and settings survive a restart? Yes. Code-Server stores them inside this server's own files, so the extensions you install and the settings you tweak stay put through any stop and start. The one thing that resets them is a reinstall — that re-downloads Code-Server itself — which is another reason to keep your actual work in a repository (below).

Code-Server vs the built-in editor

The built-in editor and Code-Server overlap, so it's worth knowing which to reach for:

File Manager editor Code-Server
Editor Monaco engine — find-and-replace, language selector Full VS Code — extensions, integrated terminal
Setup Nothing to start, no second server Its own server
Workspace The files on that server Not tied to the server your project runs on
Best for A quick edit on a live server A real, persistent development environment

Reach for the File Manager editor to tweak a config on a live server; reach for Code-Server when you want a real, persistent development environment.

Keep it updated

The Version variable (also under Settings → Environment) defaults to the latest release. To move to a specific version, set the variable and reinstall the server — reinstalling re-downloads the chosen version.

💡 Tip: A reinstall can replace files, so keep your actual work in a repository rather than only inside this editor.

What it's good for

  • Editing a project with full VS Code comforts — syntax highlighting, extensions, multi-file search, a terminal — from a Chromebook, a tablet, or a locked-down work laptop where you can't install an IDE.
  • Working on code, then shipping it — write and commit in Code-Server, push to your repository, and deploy onto your actual app server with Git deploy. That keeps editing and running cleanly separated, which is exactly how you want it.

An honest limit

Code-Server is an editor, not a hosting bundle. It's a comfortable place to write code, but your bot, website, or game server should run on its own server with the right application — Node.js, Python, Minecraft, and so on. Don't try to host your production app inside the Code-Server instance; edit here, deploy there. Think of it as your workshop, not the shop floor.

Troubleshooting

  • The page won't load — make sure the server is started, and use the exact http://address:port from the Network page (plain HTTP, the server's own port).
  • Password rejected — re-check the Password variable under Settings → Environment; if you just changed it, restart the server so the new value applies.
  • I want a newer version — set the Version variable and reinstall to pull that release.

Next steps

Was this guide helpful?