OpenVibe.Node

OpenVibe Node 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 and 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-node 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-node stop) stops every motor and keeps it stopped.

How it fits the network

Devices pair through OpenVibe.Network or OpenVibe.Bot. Bot drives robots through it, and 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.