Skip to main content
Runs the Axol web control panel, a local server that lets you drive the robot from a browser instead of a terminal. From the panel you can start, watch and stop teleoperation, gravity compensation, data collection, dataset replay and policy inference. With the one-command install, this command already runs as a system service (axol.service). It starts at boot and restarts automatically, and the control panel offers an update when a newer release exists. You run it by hand only on a development install:
Run it with sudo so the panel can set up CAN and restart the ZED daemon. Datasets go to $HF_LEROBOT_HOME, or to the panel’s Dataset root setting. When that folder is in a user’s home, each recording is owned by that user after every episode save, as with the installed service.
For a walkthrough of the control panel, from connecting to Axol and assigning cameras to running each operation, see the Web Control Panel guide.
axol serve is a trusted-LAN control service, not a multi-user authenticated API. Keep ports 8000/8001 behind the robot network or a host firewall; do not expose them directly to the internet.

​
TLS

TLS is on by default, so HTTPS pages such as the hosted VR app at axol.almond.bot can reach this machine. On first run a self-signed certificate is created in ~/.almond/vr/certs/. VR teleop uses the same certificate, so accepting it once covers both. To connect from a browser on another machine, open the printed LAN URL once and accept the certificate warning. Pass --no-tls to disable TLS entirely (plain HTTP).

​
Building the web UI

The server looks for the built web UI at web/app/dist, which exists only in a repo checkout. Without it, axol serve still runs and the API is available. Use the hosted UI at axol.almond.bot, which connects to the server directly. To serve the UI locally instead, build it once:
For details, see Build the web UI in the development install guide.

​
What it serves

Operations launched from the panel run inside the serve process, the same way as the teleop, gravity-comp, waypoints, collect-data, replay-dataset and run-policy commands. Anything those commands need on the host is needed here too: CAN, the lerobot, sim and tracker extras, and ZED access.