Case Study

Compound

One session. Four hours.
Each problem solved revealed the next.

February 2026 · Sequel to Untangled
Previously

Untangled

A developer had projects scattered across four devices. A migration script had timed out. In one hour, Amplifier bootstrapped a bare Mac Mini into a fully operational workstation.

4 → 1
Devices
54
Projects
1 hr
To productive

The infrastructure was fixed. The session could have ended there.

What Happened Next

Each Answer Led to a New Question

The session kept going. Each layer of work rested on everything that came before.

Hour 4 Enterprise Teams integration, cross-machine automation, skills
Hour 3 Story Story deck, design iteration, creative direction
Hour 2 Environment Dotfiles, shell config, terminal customization
Hour 1 Infrastructure Four devices, 54 projects, full bootstrap

None of this was planned. It was emergent—possible only because the AI held the full context and never needed to be re-explained.

Hour Two

Making It Home

Working tools are not the same as a working environment. The Mac Mini had the software—now it needed to feel like the developer's machine.

Dotfiles Synced
  • Shell aliases and shortcuts
  • Starship prompt (blue for remote)
  • Tmux config and Catppuccin theme
  • Six missing brew packages installed
  • API keys and provider config
Bugs Caught and Fixed
  • .zshrc not sourcing .zprofile over SSH
  • Starship hostname detection missed Mac Mini
  • Credential helper set to SSH but bundles fetch HTTPS
  • Four missing Amplifier bundles added
Auto-SSH on New Tab
Cmd+T drops into the Mac Mini. Cmd+Shift+L for local.
Active/Inactive Tabs
Colored tabs dim when inactive. Always know which is focused.
Machine Icons
Desktop icon for remote tabs. Terminal icon for local.
Hour Three

Documenting the Work

While still in the session, the developer directed the creation of an 11-slide story deck. Six rounds of creative refinement. The AI was the design tool.

The developer became creative director. Every detail was scrutinized—orphaned words, icon choices, headline phrasing, layout structure.

The AI held the full infrastructure context from the previous two hours while simultaneously executing design decisions, fixing CSS, obfuscating PII, and iterating on copy.

Emojis Phosphor icons
Card grid Two-column prose
Command Center Untangled
This Is the Promise Stay Until It Works
Real usernames PII obfuscated
Wrapped text Orphan-free typography
Hour Four

Then Came Teams

The developer needed to pull rich content from Microsoft Teams—text with hyperlinks, formatting, full context. Copy-paste strips the links.

# Copy a Teams message with three hyperlinks
clipboard: "Check out the PR for the new tool protocol..."
# Paste it
Plain text only. All three links are gone.
Accessibility tree
Teams buries content 10+ layers deep in Chromium. Crawl times out.
Browser agent
Clean Chromium has no Microsoft auth. Hits the login wall.
Graph API
Requires Azure app registration. Blocked by enterprise red tape.
Persistent browser session
Auth works, but Teams' JavaScript completely blocks the main thread.
Remote debugging
Teams desktop is Electron. Locked down.
The Approach That Worked

A Dedicated Edge Profile

Non-destructive. One-time login. Persistent auth. Full access.

# Launch Edge with a separate Amplifier profile
$ msedge --user-data-dir=~/.amplifier/edge-profile \
    --remote-debugging-port=9333

# Developer logs in to Microsoft once. Auth persists.

# Connect from Amplifier
agent> connect localhost:9333
Connected to Microsoft Edge

agent> navigate teams.microsoft.com
Authenticated. Chat list visible.

agent> extract chat content
Text + hyperlinks + formatting preserved.
Non-destructive
Dedicated profile. Regular browsing untouched.
One-time auth
Log in once. Cookies persist across sessions.
Full CDP access
Chrome DevTools Protocol. Read the real DOM.
The Escalation

Then It Kept Building

The initial breakthrough was reading Teams content. But the session didn't stop at reading.

1
Read Teams content
Full text, hyperlinks with URLs, message formatting.
2
Send Teams messages
Search recipients, compose, deliver. Bidirectional integration.
3
Format with rich text
Synthetic ClipboardEvent with DataTransfer to bypass CKEditor's TrustedHTML protection.
4
Auto-start on boot
macOS launch agent. Edge Amplifier profile starts headless on login.
5
Cross-machine access
Mac Mini calls back via reverse SSH. Both machines can read and write Teams.
6
Encoded as a skill
Every future Amplifier session knows the full Teams integration pattern. No re-explanation needed.
Impact
4 hours
One session. Continuous forward progress.
10+
Domains crossed
2
Custom skills
3
Automation scripts
0
Context resets

SSH. Tailscale. Git. Shell configuration. Node.js. Python. WezTerm Lua. macOS launch agents. Chrome DevTools Protocol. Microsoft Teams. CKEditor internals. Web server architecture. All in one conversation.

The Insight

Each Hour Built on Every Previous Hour

The AI didn't need to be re-taught the SSH setup when it was customizing WezTerm. It didn't need to be re-told about the Mac Mini when it was navigating Teams.

Four hours of accumulating context—hardware, software, design, enterprise, automation—in a single unbroken thread. That context didn't just persist. It compounded.

Hour one fixed the machines.
Hour two assumed the machines.
Hour three used the environment.
Hour four leveraged everything.

Amplifier

Context Compounds

The longer it stays, the more it builds.

withamplifier.com
More Amplifier Stories