No description
Find a file
Olivier Benz 8d9a44a024
Update Code to 1.113.0 (#7716)
* Update Code to 1.113.0

* Use CI build targets

The target we have been using has started throwing all sorts of errors
during the build (even without any of our patches).  After checking the
VS Code repo I think these are the ones we should actually be using.
They are way faster, too.

---------

Co-authored-by: Asher <ash@coder.com>
2026-03-26 11:39:40 -08:00
.github Update Code to 1.110.0 (#7694) 2026-03-05 23:54:52 -09:00
.tours
ci Update Code to 1.113.0 (#7716) 2026-03-26 11:39:40 -08:00
docs feat: expose --reconnection-grace-time CLI flag (#7678) 2026-03-25 11:47:58 -08:00
lib Update Code to 1.113.0 (#7716) 2026-03-26 11:39:40 -08:00
patches Update Code to 1.113.0 (#7716) 2026-03-26 11:39:40 -08:00
src feat: expose --reconnection-grace-time CLI flag (#7678) 2026-03-25 11:47:58 -08:00
test feat: expose --reconnection-grace-time CLI flag (#7678) 2026-03-25 11:47:58 -08:00
typings/httpolyglot
.dockerignore
.editorconfig
.git-blame-ignore-revs
.gitattributes
.gitignore
.gitmodules
.node-version Update Code to 1.113.0 (#7716) 2026-03-26 11:39:40 -08:00
.nvmrc
.prettierignore
.prettierrc.yaml
CHANGELOG.md Update Helm chart and changelog to 4.109.5 2026-03-03 08:24:56 -09:00
eslint.config.mjs
flake.lock
flake.nix
install.sh
LICENSE
package-lock.json chore: bump flatted from 3.3.4 to 3.4.2 (#7713) 2026-03-23 10:50:35 -08:00
package.json Suppress i18next support notice in terminal output (#7702) 2026-03-12 10:10:54 -08:00
renovate.json
ThirdPartyNotices.txt
tsconfig.json

code-server

"GitHub Discussions" "Join us on Slack" Twitter Follow Discord codecov See latest

Run VS Code on any machine anywhere and access it in the browser.

Screenshot Screenshot

Highlights

  • Code on any device with a consistent development environment
  • Use cloud servers to speed up tests, compilations, downloads, and more
  • Preserve battery life when you're on the go; all intensive tasks run on your server

Requirements

See requirements for minimum specs, as well as instructions on how to set up a Google VM on which you can install code-server.

TL;DR: Linux machine with WebSockets enabled, 1 GB RAM, and 2 vCPUs

Getting started

There are five ways to get started:

  1. Using the install script, which automates most of the process. The script uses the system package manager if possible.
  2. Manually installing code-server
  3. Deploy code-server to your team with coder/coder
  4. Using our one-click buttons and guides to deploy code-server to a cloud provider
  5. Using the code-server feature for devcontainers, if you already use devcontainers in your project.

If you use the install script, you can preview what occurs during the install process:

curl -fsSL https://code-server.dev/install.sh | sh -s -- --dry-run

To install, run:

curl -fsSL https://code-server.dev/install.sh | sh

When done, the install script prints out instructions for running and starting code-server.

Note

To manage code-server for a team on your infrastructure, see: coder/coder

We also have an in-depth setup and configuration guide.

Questions?

See answers to frequently asked questions.

Want to help?

See Contributing for details.

Hiring

Interested in working at Coder? Check out our open positions!

For Teams

We develop coder/coder to help teams to adopt remote development.