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

Connor Manraz — Fri, 10 Apr 2026 13:57:37 +0000

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

Source code: GitHub - darkerthanblack2000/open-pair
Marketplace: VS Code Extension

Automated Session Control with Bluetooth: An Insight into ble-lock-session

Connor Manraz — Sat, 23 Nov 2024 20:48:33 +0000

Introduction

ble-lock-session is a simple Python tool that uses Bluetooth to automatically lock or unlock your computer based on the proximity of a device, such as your smartphone or smartwatch. It was created to bring a touch of automation to everyday computer usage, securing your environment effortlessly and with minimal hardware requirements.

In this article, we will look into how ble-lock-session works, its underlying design, and some interesting ways you can extend its functionality beyond the basic lock/unlock mechanism.

What is ble-lock-session?

ble-lock-session is a Python-based tool that interacts with your system’s Bluetooth stack to determine whether a paired device is nearby. Based on this information, it can automatically run a command to either lock or unlock your session.

The goal is straightforward: when your device (like a phone) is detected, the computer unlocks, and when the device is no longer in range, the computer locks itself.

How Does It Work?

Here's a brief breakdown of how ble-lock-session works:

Configuration: The tool reads settings from a configuration file (config.ini), which includes the target Bluetooth device address, the commands for locking and unlocking, and intervals for checking device presence.
Bluetooth Monitoring: Using the Python bluetooth library, it regularly scans for the specified Bluetooth device. If the device is present, an unlock command is executed; if not, a lock command is triggered.
Customizable Commands: The flexibility comes from being able to configure the commands that are executed when the Bluetooth device is detected or lost. This means you aren't limited to just locking or unlocking—any command can be used, making it highly customizable.

Here’s a typical use case:

Locking your PC: gnome-screensaver-command --lock.
Unlocking your PC: gnome-screensaver-command -d (for GNOME desktops).

But the possibilities go well beyond this.

Going Beyond Session Locking/Unlocking

The original purpose of ble-lock-session was to secure your computer based on proximity, but since it runs shell commands, you can use it for a range of tasks that suit your workflow or lifestyle.

Examples of Extended Uses

Here are a few creative ways to use ble-lock-session:

Music Playback Control: Pause your music when you walk away, and resume it when you return:

  lock_cmd = "playerctl pause"
  unlock_cmd = "playerctl play"

Disable WiFi/Ethernet on Leave: Reduce distractions or conserve energy by disabling your network interface when you leave your desk:

  lock_cmd = "nmcli radio wifi off"
  unlock_cmd = "nmcli radio wifi on"

The versatility of ble-lock-session comes from being able to use any shell command, making it a powerful tool for building customized automation workflows that fit your unique needs.

A Quick Start

To get started with ble-lock-session, clone the GitHub repository and install the required dependencies:

git clone https://github.com/azratul/ble-lock-session.git
cd ble-lock-session
pip install pybluez

Scan for your Bluetooth device and configure the commands:

./ble-lock-session.py --scan

Once configured, start the lock/unlock feature:

./ble-lock-session.py --start

You can also update the configuration interactively:

./ble-lock-session.py --config

Final Thoughts

ble-lock-session is a straightforward tool that brings automation into your daily workflow with minimal setup. By leveraging the proximity of a Bluetooth device, you can lock and unlock your computer seamlessly and do much more.

This kind of flexibility is perfect for those who like to experiment with automation. Whether you use it to control your music, manage your network, or any other creative scenario, ble-lock-session can be adapted to fit your needs.

Try it out and see what kind of unique automations you can come up with.

DEV Community: Connor Manraz