# OpenVibe.Bot > An open control panel for robots: pair a robot with one pasted command and drive it from any browser, with roles, limits and a latched emergency stop on every command. ## Pages ### OpenVibe.Bot — drive your robot from any browser URL: https://openvibe.bot/ OpenVibe.Bot is the open control panel for robots. Add a robot and pick its profile, pair it by pasting one command on the robot's computer, then drive it from any browser. The panel lays its controls out from the robot's profile: a touch joystick, the keyboard, a gamepad, buttons and sliders, with a latency meter. Every command passes one gate with roles, per-robot limits, cooldowns and a turn budget, and a latched emergency stop that only the owner clears; a stop pressed on the robot itself holds until it is released there. An owner can add people by username as operators or viewers, or open a queue where visitors take turns. A simulated rover runs inside Bot, so the whole panel can be tried before any hardware exists. ### Try the panel with a simulated rover URL: https://openvibe.bot/try A rover simulated in the visitor's own browser, driven through the same OpenVibe.Bot panel a paired robot gets: a touch joystick, the keyboard (W A S D or the arrows, Space to stop) or a gamepad, with the same command shaping, deadman and latched e-stop. It has a front camera drawn from its position in a small arena, an ultrasonic distance sensor, three line sensors over a strip of yellow tape, a battery, RGB headlights and a horn. Nothing pressed there moves real hardware, and nothing needs an account. The page ends with the way to a real robot: add one, pair its computer with one pasted command, and the same panel drives it. ### Robots URL: https://openvibe.bot/robots The OpenVibe.Bot robot directory. Owners may list a robot; a listed robot has a public page where anyone can watch it live through its read-only panel, and a robot whose owner opened a queue lets signed-in visitors take timed turns at the controls. The page also lists every model Bot has a profile for, and, for a signed-in person, their own robots with the way to add one. ### Models URL: https://openvibe.bot/models The robots OpenVibe.Bot drives, grouped by how they connect: simulated (the rover that runs in Bot and in the browser), on-board (the OpenVibe Node on the robot's own computer: the Adeept ADR036 4WD car and its mecanum build, the relay robot for any Linux board), bridge (the Node on a computer or phone next to the robot: Cozmo through PyCozmo, the LOOI desk robot over Bluetooth) and server-side (ONVIF pan-tilt-zoom cameras, nothing to install). Each model has a page with how it connects, its setup steps, its guide and the controls its panel gets. ### Build for OpenVibe.Bot URL: https://openvibe.bot/docs The build index for OpenVibe.Bot. Two things are open to build against: a driver, a separate program the OpenVibe Node runs and talks to in JSON lines over stdin/stdout, and a robot profile (bot.robot-profile@1), the JSON that says what a robot can do and which widgets its panel shows. The page links the driver guide and the profile guide, and points to the OpenVibe Node plugins tree, the protocol document and the plugin contract. ### Write a driver URL: https://openvibe.bot/docs/drivers The driver protocol spec for OpenVibe.Bot. A driver is a separate executable the OpenVibe Node core starts, in any language, and the two speak JSON lines over stdin/stdout. The page covers what a driver is, the three connection kinds (on-board, bridge and server-side), the start-up lifecycle and restart rules, every message in both directions (hello, command, heartbeat, stop, estop, resume; describe, ready, fault, ack, nack, telemetry, event and video), the safety rules, a minimal Python driver, and how to test and contribute one. ### Robot profiles URL: https://openvibe.bot/docs/profiles The robot profile format (bot.robot-profile@1) that OpenVibe.Bot renders a panel from. The page lists the fields (connection kind, motion kinds, commands, widgets and limits), shows a full example, and has a validator for a profile you paste. Profiles ship with Bot, including the simulated rover (sim.rover). ### Routines, webhooks and your agent URL: https://openvibe.bot/docs/automation How a robot on OpenVibe.Bot moves without anyone at the controls, through the same gate as a person (limits, cooldowns, e-stop, audit). Steps are plain lines checked against the robot's profile: forward, back, left and right for seconds at a speed, stop, wait, say, face, show, an actuator or camera axis with a value and a hold time, and press for a button; held steps are re-sent inside the deadman window and a refused step stops the rest with its reason. Routines run steps as the owner on demand, every N minutes (at least 5), daily at a UTC time on chosen weekdays, or each time the robot comes online; one runs at a time; 60 steps, 60 seconds a step, 10 minutes in all. Webhooks send a robot's bot.robot.online, bot.robot.offline, bot.estop.set, bot.estop.cleared and bot.command.refused events to up to five https addresses, each with its own whsec_ secret shown once, signed like OpenVibe.Events deliveries (X-OpenVibe-Timestamp, X-OpenVibe-Signature-V2, checked with verifyDeliveryV2 from openvibe-sdk/events), to public addresses only, retried after 30 seconds, 2, 10, 30 and 120 minutes. The Your agent switch, off until the owner turns it on, lets the owner's OpenVibe.Actor agent see their robots and run steps on that one as the owner, never for anyone else; a steps call on Bot's API runs up to 20 steps and 30 seconds and answers done, or stopped with the reason. ### Your computer for your agents URL: https://openvibe.bot/docs/computers How to let your agents use your own computer through the OpenVibe Node's computer plugin. Installed with --computer, it runs as your own account, never root, and its only folder is your home. The level is set on the computer only: observe (screenshots, listing and reading files), ask (programs and writes each approved on the computer with openvibe-node approve), trusted (inside its folders without asking) or full. Programs are argv, never a shell line, time-limited and output-capped. The local stop drops it to observe. The switch Let my agent use this computer on openvibe.bot/machines lets your OpenVibe.Actor agent use it as you. Bot's machine commands take exec, fs and screen, and the computer's answer comes back in data. ### What shipped on OpenVibe.Bot URL: https://openvibe.bot/updates The update log of OpenVibe.Bot: every change deployed to the site, newest first, each line a commit from the OpenVibers repositories linked to the change itself. Batches of changes become Patch notes on openvibe.blog, and the whole network's log is on openvibe.network/updates. ### Terms of Service URL: https://openvibe.bot/terms The terms for using OpenVibe.Bot: who may use it, the OpenVibe account, acceptable use, what you may pair and control, and the limits of the project's liability. The service is provided as it is, without warranties. ### Privacy Policy URL: https://openvibe.bot/privacy The privacy policy for OpenVibe.Bot: what the service collects and why, the first-party cookies it sets, what is shared with the services that run the network, how long things are kept, and the choices and rights you have over your data. ### DMCA & Copyright URL: https://openvibe.bot/dmca How OpenVibe.Bot handles copyright: its position under the Digital Millennium Copyright Act, how to send a takedown notice, what happens next, counter-notices, and how repeat infringers and false claims are handled.