No description
Find a file
dependabot[bot] ada8e2bf41
chore: bump env-paths from 2.2.1 to 4.0.0
Bumps [env-paths](https://github.com/sindresorhus/env-paths) from 2.2.1 to 4.0.0.
- [Release notes](https://github.com/sindresorhus/env-paths/releases)
- [Commits](https://github.com/sindresorhus/env-paths/compare/v2.2.1...v4.0.0)

---
updated-dependencies:
- dependency-name: env-paths
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-04-01 12:48:12 +00:00
.github Use tag env var in npm publish 2026-03-30 14:36:22 -08:00
.tours
ci Prune dev dependencies when building release 2026-03-31 09:07:39 -08:00
docs Use VS Code packaging for releases (#7721) 2026-03-27 17:08:35 -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 Use VS Code packaging for releases (#7721) 2026-03-27 17:08:35 -08:00
.gitmodules
.node-version Update Code to 1.113.0 (#7716) 2026-03-26 11:39:40 -08:00
.nvmrc
.prettierignore Use VS Code packaging for releases (#7721) 2026-03-27 17:08:35 -08:00
.prettierrc.yaml
CHANGELOG.md Update changelog with 4.110.0 through 4.112.0 2026-03-27 17:11:18 -08:00
eslint.config.mjs
flake.lock
flake.nix
install.sh
LICENSE
package-lock.json chore: bump env-paths from 2.2.1 to 4.0.0 2026-04-01 12:48:12 +00:00
package.json chore: bump env-paths from 2.2.1 to 4.0.0 2026-04-01 12:48:12 +00: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.