# Home Lab pitch

> A persistent, multi-provider agent workspace that also runs useful household services

- HTML version: https://robbiepalmer.me/projects/homelab/deck
- Project: Home Lab (https://robbiepalmer.me/projects/homelab.md)
- Slides: 10

## Slide 1

# My phone reaches the same development machine as my laptop

t3-code runs on an always-on Mac mini behind Tailscale.

## Slide 2

## Four coding harnesses, one persistent workspace

*(Interactive TechIcon component — view it on the HTML page)*

t3-code
threads, worktrees and GitHub

*(Interactive div component — view it on the HTML page)*

*(Interactive TechIcon component — view it on the HTML page)*

Claude Code

*(Interactive TechIcon component — view it on the HTML page)*

Codex

G
Grok Build

*(Interactive TechIcon component — view it on the HTML page)*

OpenCode

Models come from subscriptions. Repos, tools and sessions stay on the Mac mini.

## Slide 3

## The sidebar shows where every thread stands

*(Interactive span component — view it on the HTML page)*

personal-site
Codex · running

*(Interactive span component — view it on the HTML page)*

home lab
Claude Code · needs input

*(Interactive span component — view it on the HTML page)*

recipe parser
OpenCode · ready to settle

Review diff → commit → push → open PR without leaving the thread.

## Slide 4

## The phone is a control surface. The Mac mini does the work.

```mermaid
flowchart LR
A[Phone or laptop<br/>via Tailscale] --> B[t3-code<br/>Mac mini]
B --> C[Four coding harnesses<br/>Claude Code · Codex<br/>Grok Build · OpenCode]
C --> D[Models and threads]
B --- G[Repos and worktrees]
B --- H[GitHub auth and tools]
B --- I[Browser and telemetry]
```

Every thread shares the host's repos, tools, GitHub auth, browser, and telemetry.

## Slide 5

A finished change includes proof from the running system

agent worktree
evidence bundle

WORKTREEReal repo, isolated branch✓
COMMANDChecked-in mise task✓
TARGETRestarted service or protected preview✓
PROOFBrowser result, health response and logs✓

The pull request carries the evidence. Real Android and iOS can join the bundle later.

## Slide 6

## Every layer becomes part of the next build

NextPhone labPreview checks on real Android and iOS
EvidenceBrowser + telemetryVisible results from running services
Repeatmise + worktreesShared commands and isolated changes
Workt3-codePersistent threads, repos and credentials
ReachTailscalePrivate access from phone or laptop

The next project starts four working layers ahead.

## Slide 7

## Old hardware gets jobs that suit the hardware

Mac miniAgent sessions, services and the 10TB disk
Raspberry PiFallback DNS and a USB print server
NixOS desktopGTX 1050 worker and 1TB DVC cache
Retired phonesProposed browser targets and cellular watchdog

A NAS is easier. Reusing the Mac and printer avoids two purchases.

## Slide 8

## Cloud services stay where they earn their keep

KeepEnteEncrypted cloud sync, plus plain-file backup in the lab
KeepAI subscriptionsModels stay; t3-code replaces their remote interfaces
KeepTraktDiscovery and history, with Jellyfin for owned media
AvoidNew printer or NASCUPS revives the printer; ordinary disks avoid appliance lock-in

A better owned library may make some streaming subscriptions unnecessary.

## Slide 9

## The Mac mini concentrates three failure modes

one host
Mac mini
agents · credentials · photos

Outage
Remote coding stops

Permissions
Agents share a host with personal data

Backup
The second copy stays in the same house

Accept outage · isolate agent storage · add an off-site copy

## Slide 10

# Reuse the pattern on hardware you already own

Use hardware you already own. Add private remote access, one agent interface, repeatable commands, and checks against
the running system.

Fork the repo. Keep the decisions that solve a problem you actually have. Delete the rest.

---

Markdown index of this site: https://robbiepalmer.me/llms.txt