HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
xaberus
vscode-remote-oss
TypeScript2022–2025
xaberus / vscode-remote-oss

vscode-remote-oss

Remote development for OSS Builds of VSCode like VSCodium

7Distinct people
8Mentions
0Explicit recommenders
132GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Remote development for OSS Builds of VSCode like VSCodium

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year8 dated mentions

Observed mentions: 2022-06-12 16:40:01 UTC to 2025-07-27 20:02:23 UTC.

0122022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

What Hacker News says

8 sources
No? The non-free binary is the client not the server. There are free implementations of the client for Code OSS. The server installed on the remote machine is part of vscode itself called the REH (remote extension host). It’s the core of the editor running in headless mode on the server. Here is an example open source implementation of the non-free binary client (it’s a 4 files that call various editor APIs) https://github.com/xaberus/vscode-remote-oss This is REH entry (the binary installed on the remote machine) https://github.com/microsoft/vscode/tree/main/src/vs/server/...
In Disabling telemetry in ByteDance's VSCode fork increases data sent to its server
That’s the extension which launches the server. The server itself, which is what runs on the remote machine, is part of the vscode repo itself. You can see this open source extension for an example of what the extension does as well as an explanation of what it does https://github.com/xaberus/vscode-remote-oss Mainly just sets up the UI/connect commands in vscode UI and launched REH (the vscode server) on the remote machine. The actual server is just a different binary you build from the same repo. Non-Microsoft OSS builds of vscode work with SSH fine.
In SSH Remoting
I’ve started using Remote OSS [0] with some custom scripts to install and run the remote code host. Works great on remote servers and even with devcontainers on remote hosts. You can use a script like the one here to handle automatically installing and setting up the tunnel [1]. I’m working on a PR that adds a way to automatically run custom scripts to set up the tunnels as well [2]. [0] https://open-vsx.org/extension/xaberus/remote-oss [1] https://github.com/CGamesPlay/dotfiles/blob/master/files/.lo... [2] https://github.com/xaberus/vscode-remote-oss/pull/9
In VSCodium – Open-source binaries of VSCode
The extension API proposals and RPC protocol are open sourced and the server code is just an electron-less version of the regular VSCode extension host (hence, remote extension host, REH). This is all part of the VSCode OSS release. What the proprietary extensions provide is integration. For example, the SSH variant automatically installs and launches an REH instance on the remote host and sets up port forwarding. If you are willing to start the instance and to forward ports yourself, you can use the tiny extension I wrote [1,2] (See the README how to enable the necessary extension proposals.). It allows you to connect to a local port you configure in the config. It is based on an example extension (vscode-test-resolver) in the OSS release that is used to test this functionality [3]. Microsoft is not really hiding any of this, so I am a
Read the rest
In I’m switching from VS Code to VS Codium

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.