Skip to main content

Controlling the OTA Bootstrap

The bootstrap service polls https://cdn.autonomous.ai/os/ota/metadata.json and applies any component (os-server, HAL, web, bootstrap itself) whose official version is newer than what's on disk. Left running, it will overwrite any custom os-server / HAL / web build you pushed with scp, usually within a minute — the Intern team ships OTAs on their own cadence and there is no way to opt out per-file. If you're doing custom development, disable bootstrap first (see Building + Shipping Code) and only re-enable it when you want your device to snap back to the official fleet build.

# Stop for one session (survives until next boot)
sudo systemctl stop bootstrap

# Persist across reboots — nothing OTA will hit this device
sudo systemctl disable --now bootstrap

# Re-enable when you're done developing
sudo systemctl enable --now bootstrap

To confirm nothing else is overwriting your binary, tail the bootstrap log before and after your push:

sudo journalctl -u bootstrap -f