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

Download, open, pick a model

Sign in, download r1o, drag it to Applications, and open it. That is the whole install: the agent, asmi, and model management come bundled. No Homebrew, pip, or Docker.

r1o

r1o for macOS

For Apple Silicon Macs

On first launch, r1o scans your ~/Models directory and any Hugging Face 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

One Mac, one local model.

That is a complete setup: a model running on your Mac, with nothing sent anywhere else. Everything after this is optional: more devices, more Macs, bigger models.

Next: Your Private Network
2Chapter 2

Your Private Network

Connect your devices over Tailscale

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

With Tailscale on each device, your Macs reach each other on a private network, wherever they are. The iPhone and iPad app is coming soon: it will find your Mac over the same network, and the model keeps running on the Mac.

Mac
Tailscale mesh
iPhone, coming soon

Encrypted end to end, and direct whenever the network allows.

Next: Add More Macs
3Chapter 3

Add More Macs

Each Mac adds memory for bigger models

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

Move models between Macs over Thunderbolt 5

Connect your Macs with Thunderbolt 5 cables. From macOS 26.2, Macs can use RDMA over them: direct memory access at Thunderbolt 5 speeds. That is how the cluster moves model weights between Macs.

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 shows every active RDMA link. On our own four-Mac cluster, model transfers ran at 5.5 GB/s over RDMA, against about 100 MB/s on gigabit Ethernet: a 40 GB model in about 7 seconds instead of about 7 minutes.

100 MB/s

Gigabit Ethernet

55x

5.5 GB/s

RDMA, measured

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 Hugging Face, 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 agent that speaks MCP can manage your models: the r1o Agent, Claude Code, and Cursor 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

Tools, skills, and your whole cluster

The r1o Agent ships inside r1o, so there is nothing else to install. It runs on your Mac, speaks MCP, and can use every tool in the app: model management, cluster operations, and your knowledge base. Its model can be local, or a provider you connect.

r1o Agent
❯Click Run to start

Teach it your workflows with custom skills: markdown files that describe a procedure, which the agent reads and follows. With a local model, your conversations stay on 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, so the agent remembers what you teach it

One agent, wherever you work.

The Mac app today, and the iPhone and iPad app when it launches. Each one talks to the same agent, running on your hardware, on your network.