Skip to main content

Autonomous Intern 2

This guide walks a Developer Edition owner through the workflows they need on day one: SSH into the device, ship code changes, watch logs, and hit the HAL and OS Server APIs. Everything below assumes the Intern v2 Pro (OrangePi sun60iw2) shipped with SSH open and Codex / Claude Code / OpenCode pre-installed.

Developer Edition only

You can tell the editions apart by the case colour of the unit you bought:

  • Black case → Developer Edition. SSH is open, the on-device toolchain (Codex / Claude Code / OpenCode) is pre-installed, and every workflow in this guide applies.
  • Yellow case → OpenClaw edition. Consumer image, SSH is closed, no developer toolchain. This guide does not apply.
  • Blue case → Hermes edition. Consumer image, SSH is closed, no developer toolchain. This guide does not apply.

If your unit is yellow or blue and you need the developer workflows below, you'll need a Developer Edition (black) unit — the consumer images cannot be unlocked in the field.

The source of truth is the autonomous-os repo. Every file path in this guide is relative to that repo unless noted otherwise.

What's in this guide​

  1. Device Access — SSH in, the on-device filesystem layout, and the browser-based Web CLI.
  2. Logs — tail every service with journalctl.
  3. Configuration — LLM/STT/TTS config and HAL runtime env.
  4. Building + Shipping Code — cross-compile Go, sync Python HAL, build the Web UI.
  5. Controlling the OTA Bootstrap — stop the fleet updater from overwriting your custom build.
  6. HAL API — TTS, STT, mic, speaker, and LED endpoints.
  7. MQTT — add a new device command end to end.
  8. Web UI — Setup and Admin SPA routes.
  9. Repo Map — what lives where in autonomous-os.
  10. Further Reading — deeper docs in the source repo.
  11. Getting Help & Buying — where to buy a Developer Edition unit and get support.