How Coder IDE Works: Install, Approve, Open

Coder IDE lets you open the VS Code on your own computer from a phone, a tablet or any browser. Setting it up takes three steps and about a minute: install, approve, open. This post walks through each step, then explains what actually runs on your computer, how your other devices reach it, and what keeps itself up to date so you don't have to.

What you need

Two things: the computer you want to code on, and a device to code from.

The computer can run Windows, macOS, Linux or WSL. It's where your projects, your toolchain and your extensions already live, and it keeps doing all the work. It can also be a remote Linux server you reach over SSH.

The device can be anything with a modern browser: a laptop, a Chromebook, an iPad, an Android phone or tablet. Android also has the Coder IDE app, with a key bar, stylus support and layouts for phones, tablets, TVs and watches. On iPad and iPhone you use the browser, and you can install Coder IDE as a web app from the share menu.

Step 1: Install with one command

The install command is on the Coder IDE website and in the setup guide on your dashboard. There's one for macOS, Linux and WSL, and one for Windows PowerShell. The site picks the right one for the computer you're on, and you can switch between them. Copy it, paste it into a terminal on the computer you want to code on, and run it.

The installer sets up two things: a small background app that keeps your computer connected, and the Coder IDE desktop app, which opens when the install finishes. The desktop app lives in your system tray, or the menu bar on macOS. It's where you sign in, see which editors are running, check forwarded ports, read logs and change settings.

You run the installer once. After that, everything updates itself, which we cover below.

Step 2: Sign in and approve the computer

In the desktop app, click Sign in. Your browser opens with a short code. Sign in to Coder IDE if you aren't already, check that the code matches the one on your computer, and approve it.

This step is the security model. A new computer only joins your account after you confirm its code from a browser you're signed in to. The approval page tells you which computer is asking, and warns you if it's on a different network than you are. If a request shows up that you don't recognise, deny it instead of letting it expire.

Once approved, the background app sets itself up to start with your computer. Your system asks for administrator permission once. From then on it restarts after crashes and stays connected, with the editor itself switched off until you open it.

Two optional stops in the desktop app's Settings are worth a minute:

• Settings and extensions. Choose what the editor starts with: your cloud settings, or the setup of an editor already on the computer, such as VS Code or Cursor.
• Run checks. A self-check that tests sign-in, the background app, startup, the editor and the connection, so you know everything is green.

On a server with no desktop, run coder-ide login over SSH instead. It's the same flow: a code in the terminal, approved from your browser.

Step 3: Open it from anywhere

Within a few seconds, the computer shows up on your dashboard as online. Each folder you work in becomes its own project, so a work repository and a side project don't share one window.

Tap Open and you're in VS Code: your extensions, settings, keybindings and integrated terminal. If that project's editor isn't running yet, the button says Connect and starts it for you.

There's no port forwarding, no VPN and no certificates to set up. It works behind NAT and firewalls, from home Wi-Fi, a café or mobile data. On a phone, you get the same editor, and you can switch between your projects without leaving it.

What runs on your computer

Three pieces, all on your machine:

• Microsoft's VS Code server. The same editor Microsoft ships, served to your browser. That's why your extensions work the way they do on the desktop.
• The background app. It keeps the connection open, starts and stops editors when you ask, lists the dev servers you're running, and reports your Claude Code sessions so you can follow them from your phone.
• The desktop app. Your window into all of this on the computer itself. It shows running editors with their idle countdown, forwarded ports, logs, and settings such as launch at login.

Your code, your terminals and your builds never leave the computer. A phone only has to draw the interface, which is why a large TypeScript project feels the same on a phone as it does at your desk.

Editors don't need to run all day. Turn on auto-suspend and an idle editor shuts down after a timeout you choose, from the dashboard or the desktop app. If Claude Code is in the middle of a task, auto-suspend waits for it to finish.

How your devices reach it

When you're away from home, a relay forwards traffic between your device and your computer. The relay passes the connection along. Your code stays home.

When your device is on the same network as your computer, the editor connects to it directly instead, which is faster. It switches between the direct connection and the relay on its own when you change networks, and falls back to the relay automatically if the direct connection fails. You don't choose between them.

Access is tied to your account at every step. Signing in uses a one-time email link or Google, so there's no password to leak. Every computer is approved by you, and removing a device from the dashboard stops its access immediately. The security section on our home page covers this in more detail.

What keeps itself up to date

Coder IDE is built so you never re-run the installer:

• The background app updates itself when it's idle. If you'd rather hold a computer on its current version for a while, each device on the dashboard has a switch to pause updates.
• The editor stays up to date automatically, so you get new VS Code releases without doing anything.
• The desktop app updates itself too. Its Settings have an Updates section showing the editor's version, with a button to check for updates now.
• Updates wait for Claude. If Claude Code is working on something, an update on your computer waits until it's done.
• The Android app asks you to install each new version as soon as it's out, and installs it in a tap.

If an older version on your computer can't handle something new you asked for from your phone, you're told to update it instead of being left waiting.

Wrap-up

Install once, approve the computer from your browser, and open its VS Code from whatever device is in your hand. Everything runs on your own machine, the relay only forwards traffic, and the pieces keep themselves current. For the bigger picture of why your own computer makes a good remote workspace, see your computer is your cloud dev environment. The how it works section on our home page has a short demo of the approval step.

Start free. The free plan covers one computer, and Pro adds unlimited devices.