Case Study

Untangled

Four devices. Dozens of broken projects.
One hour to fix everything.

February 2026
The Situation

The Multi-Device Mess

A developer experimenting with Amplifier across every machine he owned. Projects scattered. Migrations half-finished. Nothing worked end to end.

MacBook Pro
10.x.x.93
Command center
Mac Mini
10.x.x.85
Target machine
Raspberry Pi
10.x.x.59
Source of truth
MacBook Pro 2
10.x.x.56
Offline

Connected via Tailscale. A migration script from Pi to Mac Mini had timed out mid-transfer, leaving everything in a split state across weeks of fragmented sessions.

The Diagnosis

First Assessment: Not Good

Amplifier's session analyst swept weeks of history across devices. The initial report painted a dire picture.

Live OS
181MB source. Empty on Mac Mini. The developer's most critical project—apparently missing entirely.
amplifierOne
149MB source, only 300KB transferred. Practically empty shell. Severe data loss from the timeout.
PiBrowser
1.6GB source, only 2.3MB arrived. 99.8% of the data never made it across.

Plus: no Homebrew, no GitHub CLI, Amplifier not in PATH. The Mac Mini was practically bare.

Ground Truth

Then We Actually Looked

Session logs told one story. SSH told another.
Never trust the report when you can check the machine.

# SSH into both machines simultaneously via Tailscale
macmini $ du -sh ~/projects/lifeos
181M ~/projects/lifeos

pi $ du -sh ~/projects/lifeos
181M /home/pi/projects/lifeos

# 181M = 181M. It's all there.
# The repair script had run after all. The analyst was wrong.

macmini $ which brew
brew not found
macmini $ which gh
gh not found
macmini $ which amplifier
amplifier not found

# Data: safe. Tools: missing. That we can fix.
The Build

Bootstrap a Bare Machine

System Python 3.9.6 and nothing else. Clock starts now.

+0:05
Install uv + Homebrew in parallel
Python tooling and package manager bootstrapped simultaneously.
+0:10
Install gh, node, amplifier, amplifier-dev
gh and node were already in brew's cellar—just invisible to PATH. Amplifier installed fresh from git source.
+0:15
Verify GitHub authentication
SSH keys confirmed. Hi developer! Push and pull both working.
+0:20
Verify every key project
lifeos: clean git, 25 sessions, submodules intact. withamplifier: pulled 93 new files, npm installed, Next.js builds clean. 54 session histories confirmed.
+0:25
Rescue corrupted duplicate
Found two copies of withamplifier—one with a corrupted git pack. Rescued an orphaned transcript, consolidated to the good copy.
The Workflow

Make the Remote Feel Local

The Mac Mini is the engine.
The MacBook is the cockpit.
Everything needs to feel like it's right here.

Auto-SSH Terminal
WezTerm configured so Cmd+T drops straight into the Mac Mini. Cmd+Shift+L for a local tab when needed. No typing ssh ever again.
Dev Server Access
SSH port forwarding for localhost, plus direct Tailscale URLs. Dev servers bound to 0.0.0.0. Both paths work—pick whichever fits.
Visual Distinction
Blue Starship prompt on the Mini. Yellow on the MacBook. Machine icons in tab titles. Active/inactive dimming on colored tabs.
# From the MacBook browser
$ curl -s -o /dev/null -w "%{http_code}" http://10.x.x.85:3000
200
# withamplifier loads in under 1 second via Tailscale
Environment Parity

Make It Feel Like Home

A dotfiles repo held the whole setup. It just needed to land on the right machine—with a few fixes along the way.

Synced from Dotfiles
  • Shell aliases and shortcuts
  • Starship prompt (server theme: blue)
  • Tmux config + Catppuccin theme
  • WezTerm configuration
  • API keys (Anthropic, OpenAI, Google)
Bugs Found & Fixed
  • .zshrc not sourcing .zprofile over SSH
  • Starship theme detection missed Mac Mini hostname
  • gh credential helper set to SSH, but bundles fetch via HTTPS
  • Amplifier settings missing 4 bundles
  • 8 missing brew packages installed

Every change committed and pushed. Reproducible on any future machine with git clone && ./install.sh

The Transformation

Before & After

Before
  • Projects scattered across 4 devices
  • Migration script timed out
  • No brew, no gh, no amplifier
  • Corrupted git repos
  • Password prompts every session
  • No remote dev workflow
  • Days of lost productivity
After
  • Single command center workflow
  • 54 projects verified and accessible
  • Full tool parity between machines
  • Git push/pull working seamlessly
  • Zero credential prompts
  • Auto-SSH, port forwarding, Tailscale
  • Ready to ship
Impact
1 hour
From scattered chaos to fully productive.
4 → 1
Devices consolidated
54
Projects migrated
96+
Repos accessible
7
Problem domains crossed
The Insight

None of This Was Hard.
All of It Was Impossible.

No single step here was brilliant. Install brew. Copy a file. Fix a PATH. Individually, each one is a search result away.

What was impossible before is holding the full context of a complex, messy, real-world situation—across hardware and software—making a plan, executing it, verifying it works, and keeping going until the human is actually productive.

Seven domains in one conversation.
Four machines operated simultaneously.
Self-correcting in real time.
Sixty minutes of continuous forward progress.

Amplifier

Stay Until It Works

Hold the full context. Cross every domain.
Keep going until the human is productive.

withamplifier.com
More Amplifier Stories