---
title: "OpenVibe.Link · OpenVibe.Wiki"
canonical: "https://openvibe.wiki/w/openvibe/openvibe-link"
updated: null
---

# OpenVibe.Link · OpenVibe.Wiki

HTML: [OpenVibe.Link · OpenVibe.Wiki](https://openvibe.wiki/w/openvibe/openvibe-link)

# OpenVibe.Link

[1 source cited](/w/openvibe/openvibe-link/sources) [1 revision](/w/openvibe/openvibe-link/history) this text accepted 2026-11-09 Not yet reviewed by a person

**Imported, written with AI assistance.** Imported from the OpenVibe repository README and STATUS files at the cited commits, summarised with AI assistance; originally by OpenVibers. Not yet reviewed by a person.

| Repository | [github.com/OpenVibers/OpenVibe.Link](https://github.com/OpenVibers/OpenVibe.Link) |
| --- | --- |
| Runtime | Go (one static binary per platform), plugins in Go and Python |
| Status | released (v0.9.x) |

**OpenVibe Link** runs on a person's own devices: computers, servers, Raspberry Pis, phones and robots. Paired once with OpenVibe, it lets products such as [OpenVibe.Bot](/w/openvibe/openvibe-bot) and [OpenVibe.Actor](/w/openvibe/openvibe-actor) use the device.

## What it does

- **The core** is one static Go binary per platform.
- It connects out over one WebSocket and needs no open ports.
- It keeps heartbeats, a deadman and a persisted emergency stop, and owner limits are clamped before any driver sees a value.
- It publishes video over WHIP.
- It installs as a system service on Linux, macOS and Windows.
- **Plugins** run as separate processes: robot drivers (Adeept, Cozmo, ROS 2, and the community's LOOI driver) and the computer plugin. Every plugin stops its own actuators when its link goes quiet.
- **The computer plugin** lets an AI agent work on the machine only at the level its owner sets:
- reading the screen;
- files;
- a terminal;
- the mouse and keyboard;
- a browser of the agent's own, in its own profile.

 At the "ask" level, each action waits for the owner's approval on the machine. The owner can answer from the tray
 (`openvibe-link tray`, on Linux and Windows), from a notification's Approve and Deny buttons, from a dialog on macOS,
 or from the command line. An approval is not taken while the agent itself is using the mouse or keyboard.

- **The local kill switch** (`openvibe-link stop`) stops every motor and keeps it stopped.

## How it fits the network

Devices pair through [OpenVibe.Network](/w/openvibe/openvibe-network) or [OpenVibe.Bot](/w/openvibe/openvibe-bot). Bot drives robots through it, and [OpenVibe.Actor](/w/openvibe/openvibe-actor) uses its computer plugin for computer control.

## Status

Released as versioned binaries. Mouse and keyboard input arrived in v0.9.0, the browser in v0.10.0, and approvals from the desktop in v0.11.0.

## Sources

1. [OpenVibe.Link README (commit bf0ebb9)](https://github.com/OpenVibers/OpenVibe.Link/blob/bf0ebb9e0b43e89beec8e855ef3fdecbba96c1c7/README.md), retrieved 2026-10-14

   One service for your computers, servers, Raspberry Pis, phones and robots

[Inspect these sources](/w/openvibe/openvibe-link/sources) (retrieval times, where each was first cited, what changed between revisions)

## What links here

- [OpenVibe](/w/openvibe/openvibe)
- [OpenVibe.Actor](/w/openvibe/openvibe-actor)
- [OpenVibe.Bot](/w/openvibe/openvibe-bot)
- [OpenVibe.Watch](/w/openvibe/openvibe-watch)

## Discussion

No comments yet

Start the discussion about this page.

[Sign in to comment](/auth/login?next=%2Fw%2Fopenvibe%2Fopenvibe-link)

[Sign in](/auth/login?next=%2Fw%2Fopenvibe%2Fopenvibe-link) to comment.