Back to home

The r1o Guide

From a single Mac to a private AI cluster. Each chapter is a self-contained milestone — stop at any point and have something working.

1Chapter 1

One Mac, One Model

Five minutes from download to private AI

Download r1o.dmg, drag it to Applications, open it. That is the entire install. asmi, Hermes, the dashboard, model management — everything is bundled. No Homebrew, no pip install, no Docker.

r1o

r1o for macOS

Apple Silicon (M1+) -- ~80MB

On first launch, r1o scans your ~/Models directory and any HuggingFace cache automatically. If you already have MLX models downloaded, they show up instantly. Pick one from the Models tab, hit Deploy, and start chatting.

r1o -- First Launch
Click Run to start

Five minutes from download to private AI.

You now have a local LLM running on your Mac. No accounts, no API keys, no data leaving your machine. Everything that follows is optional — scaling up.

Next: Your Private Network
2Chapter 2

Your Private Network

Chat from any device on your mesh

Tailscale creates an encrypted WireGuard mesh between your devices. Install it on your Mac and sign in — that is all. No port forwarding, no firewall rules, no cloud relay. Every device on your Tailscale network can reach your Mac directly.

Terminal -- Tailscale Setup
Click Run to start

Now open r1o on your iPhone or iPad. It discovers your Mac automatically over the Tailscale mesh. Chat from any device — the couch, the office, your commute. The model runs on your Mac; the phone is just a window into it.

Mac Studio
Tailscale mesh
iPhone

Encrypted, peer-to-peer. No cloud relay.

Next: Add More Macs
3Chapter 3

Add More Macs

Scale your cluster in minutes

Open r1o on a second Mac. If it is on the same Tailscale network, it joins automatically. The dashboard shows both nodes in the topology view — chip model, RAM, running models, everything visible from one screen.

Scanning Tailscale mesh... 0/4 found

Transfer models between nodes directly from the dashboard. Over Thunderbolt 5, transfers run at 5.5 GB/s. Over LAN, it falls back to rsync — slower, but it just works. Deploy a model to any node with one click.

hub

M3 Ultra -- 512 GB

23 models -- serving Qwen3.5-32B

Node 2

M3 Ultra -- 512 GB

18 models -- idle

Next: Thunderbolt RDMA
4Chapter 4

Thunderbolt RDMA

55x faster transfers over cable

Plug Thunderbolt 5 cables between your Mac Studios. macOS 26.2+ supports RDMA over these cables — direct memory access at Thunderbolt 5 link rates. This is how the cluster shares model weights at datacenter speeds.

One-time setup: reboot into Recovery OS, run rdma_ctl enable, reboot normally. Two minutes per node. Physical access required.

Recovery OS -- Enable RDMA
Click Run to start

The topology view in the dashboard lights up with neon cables showing active RDMA links. Model transfers jump from ~100 MB/s over LAN to 5,500 MB/s over RDMA. A 40 GB model transfer takes 7 seconds instead of 7 minutes.

100 MB/s

LAN transfer

->55x

5.5 GB/s

RDMA transfer

Next: Distributed Inference
5Chapter 5

Distributed Inference

Run models too big for one machine

Some models are too big for a single Mac. GLM-5.2 at 743 billion parameters needs over 400 GB of RAM just for the weights. No single machine can run it. JACCL splits the model across RDMA-connected nodes — you deploy, it figures out the sharding.

Terminal -- Distributed Deploy
Click Run to start

How distributed inference works

1JACCL reads the model manifest and your cluster topology
2Layers are assigned to nodes based on available RAM
3Each node loads its shard into unified memory
4During inference, activations flow between nodes over RDMA
5The API endpoint is on the coordinator — clients see one model
Next: Model Intelligence
6Chapter 6

Model Intelligence

Search, discover, and manage your models

The Models tab in Mission Control is more than a file browser. Search by natural language — "fast coding model under 50GB" — and get ranked results with RAM fit estimation for every node in your cluster.

Click an example query above to see results

Download models directly from HuggingFace, delete old ones, transfer between nodes. The model registry tracks everything: size, quantization, architecture, community benchmarks, which nodes have a copy.

13 MCP tools for model management

Any AI agent that speaks MCP can manage your models. Claude Code, Cursor, Hermes — they all get the same tools.

list_modelsmodel_detailsearch_modelsrecommend_modelmodel_fitmodel_paramsscan_modelsdownload_statustransfer_modelenrich_modelsembed_modelsadd_modeldelete_model
Next: Your AI Agent
7Chapter 7

Your AI Agent

Hermes manages your cluster

Hermes is the on-device AI agent that manages your cluster. It ships inside r1o — not a separate install, not a cloud service. Hermes speaks MCP and has access to every tool in the system: model management, cluster operations, your personal knowledge base.

Hermes -- AI Agent
Click Run to start

Teach Hermes your workflows with custom skills. Skills are markdown files that describe procedures — Hermes reads them and executes the steps. Your conversations never leave your network.

Model Management

Deploy, transfer, benchmark, and optimize models across your cluster

Cluster Operations

Monitor nodes, check health, manage RDMA topology, restart services

Knowledge Base

Personal wiki with semantic search — Hermes remembers what you teach it

One endpoint for everything.

iPhone, iPad, web, CLI — they all connect to Hermes. Your AI agent, running on your hardware, on your network. That is r1o.