VS Code in the browser
Go to file
2021-02-09 12:19:39 -06:00
.github refactor: rename doc to docs 2021-02-03 09:46:35 -07:00
.tours refactor: rename doc to docs 2021-02-03 09:46:35 -07:00
ci release-github-draft.sh: Remove incorrect assets reference 2021-02-05 15:11:16 -07:00
docs Remove Node browser shim 2021-02-09 10:40:14 -06:00
lib/vscode Resolve browser telemetry conflict 2021-02-09 11:11:38 -06:00
src Expose proxy server to plugins 2021-02-09 12:19:39 -06:00
test Re-export express for plugins 2021-02-09 12:19:38 -06:00
typings Expose proxy server to plugins 2021-02-09 12:19:39 -06:00
.dockerignore Simplify packaging and improve scripts 2020-05-08 01:04:24 -04:00
.editorconfig Add back .editorconfig 2020-02-19 14:22:14 -05:00
.eslintrc.yaml Re-export logger field for plugins 2021-02-09 12:19:36 -06:00
.gitattributes browser: Add favicon.afdesign 2021-01-08 23:03:34 -05:00
.gitignore refactor: rename doc to docs 2021-02-03 09:46:35 -07:00
.ignore Rename dev/container -> dev/image 2020-06-03 15:45:16 -04:00
.prettierrc.yaml Shake CI and docs up 2020-02-14 19:46:17 -05:00
.stylelintrc.yaml Fix bugs in CI 2020-02-18 19:06:35 -05:00
install.sh refactor: rename doc to docs 2021-02-03 09:46:35 -07:00
LICENSE.txt Shake CI and docs up 2020-02-14 19:46:17 -05:00
package.json feat: update version in package.json to 3.8.1 2021-02-05 14:07:00 -07:00
README.md docs: update code coverage badge 2021-02-05 14:13:26 -07:00
ThirdPartyNotices.txt Add ThirdPartyNotices.txt 2020-07-16 19:01:09 -06:00
tsconfig.json chore: update ts config and jest config 2021-01-25 16:34:32 -07:00
yarn.lock test: Switch from leaked-handles to wtfnode (#2604) 2021-02-01 11:06:49 -05:00

code-server · "GitHub Discussions" "Join us on Slack" Twitter Follow

Lines

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

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

Getting Started

There are two 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; see Installation for instructions applicable to most use cases

If you choose to 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.

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

Cloud Program ☁️

We're working on a cloud platform that makes deploying and managing code-server easier. Consider running code-server with the beta flag --link if you don't want to worry about

  • TLS
  • Authentication
  • Port Forwarding
$ code-server --link
Proxying code-server to Coder Cloud, you can access your IDE at https://valmar-jon.cdr.co

FAQ

See ./docs/FAQ.md.

Want to help?

See CONTRIBUTING for details.

Hiring

We (@cdr) are looking for engineers to help maintain code-server, innovate on open source, and streamline dev workflows.

Our main office is in Austin, Texas. Remote is ok as long as you're in North America or Europe.

Please get in touch with your resume/GitHub if interested.

For Organizations

Visit our website for more information about remote development for your organization or enterprise.