Bridging VS Code and Neovim for Peer-to-Peer Collaboration

#development #neovim #vscode

A look at direct TCP tunneling for teams that want to pair without going through the cloud.

Remote collaboration tools usually rely on a lot of abstraction. VS Code Live Share is the obvious example: it works well, it is easy to set up, and for most teams that is more than enough. The trade-off is that the experience depends on managed infrastructure, third-party services, and account-based authentication.

That is where Open-Pair gets interesting. It explores a different approach built around direct TCP tunneling, with a focus on keeping the connection path simple and under the user's control.

Direct connectivity, with fewer moving parts

At the center of Open-Pair is a straightforward networking idea. Instead of sending a session through a central relay, the extension connects participants more directly. The model depends on network access and secure tokens, rather than a cloud identity provider sitting in the middle.

That makes the connection path easier to inspect and reason about. For people working inside private VPCs, isolated environments, or security-sensitive projects, that level of control can matter a lot(trust me, A LOT). It also avoids some of the extra platform overhead that tends to come with fully managed collaboration tools.

A practical bridge into the Neovim world

One of the most interesting things about Open-Pair is who it is for. It gives VS Code users a way to collaborate with someone working from a Neovim setup.

Right now, the extension is built around the Guest role. The expected workflow is simple: a host starts the session from a Neovim-based environment, and the VS Code user joins through Open-Pair.

That setup has a few clear advantages:

- Neovim users keep their own environment. Anyone with a heavily customized terminal workflow can stay in it, without having to switch tools for a pairing session.
- The terminal experience feels real. Because the connection is direct, collaborators are seeing the actual machine state on the host side, including aliases, local binaries, and environment variables.
- No account setup is required. A shared session can start without asking everyone to sign into Microsoft or GitHub first.

Still early, and pretty honest about it

Open-Pair is still a work in progress, and that matters.

At the moment, it doesn't let you host sessions from VS Code. It only works as a client for joining sessions that started in Neovim. The feature set is intentionally narrow. The focus seems to be on getting the tunnel working reliably and keeping the tool lightweight. There is no built-in chat, no voice layer, and no extra collaboration dashboard. It is mostly code and terminal sharing.

For people in DevOps, SRE, or adjacent roles, that kind of scope can actually be appealing. The project feels small enough to understand, and its limitations are easy to see up front.

Final thoughts

Open-Pair is a neat idea for developers who care about controlling their own collaboration setup and who already spend a lot of time in terminal-first workflows. It also makes sense for mixed-editor teams where one person lives in Neovim and the other prefers VS Code.

Anyone curious about pairing without a cloud relay in the middle will probably find it worth a look. It is also the kind of project that benefits from real-world testing and feedback while it is still taking shape.

Project resources