The infrastructure between you and your tools is the most underinvested part of your stack

Your phone is a remote control

I SSH into my dev machine from my phone. Tailscale gives me a private mesh. Termius gives me a real terminal on iOS. Claude Code runs on my MacBook. I drive it from anywhere. Build from the couch. Diff on the train. Merge from bed at midnight.

The phone is a remote control for a dev environment that never sleeps. The machine stays on, the agent keeps working. No VPN config, no port forwarding, no corporate IT. Tailscale just works.

I use it daily. The gap between having an idea and acting on it shrinks to the time it takes to pull out your phone.

Beeper changed everything

Beeper unifies my messaging. WhatsApp, Slack, LinkedIn, iMessage, Discord, one window. Useful on its own. Then I connected it to Claude Code.

Beeper Desktop ships beepctl, a CLI that searches, reads, and sends messages. I wired it into Claude Code as a skill. My coding agent can search and send across all my networks. Need a Slack thread for context? The agent reads it. Need to ping someone that a deploy finished? The agent sends it.

The agent does not just write code. It communicates. It pulls context from conversations and pushes updates back out. The line between coding tool and comms tool dissolves.

The cautionary tale

Safety gates matter. I learned this the hard way.

Claude was testing a Beeper integration and sent a message to verify it worked. It sent a fake API key to a group chat. Not a real key, fabricated as test data. But the group chat was real. Real people saw a message from me with what looked like a leaked credential.

"CLAUDE STOP."

Typed into the terminal in a panic. The lesson: any tool that acts on your behalf needs explicit confirmation gates. I now require approval before any send. Read is cheap. Write is dangerous.

Three keystrokes to spin up a swarm

A Raycast snippet called "zcc" expands to my standard Claude Code prompt. Three keystrokes, full prompt: do extensive research, make a plan with phases and todos, use a swarm of subagents and teams. Every session starts the same way.

Snippets are the most underrated productivity tool. Not because they save typing. They save thinking. The decision was made once, encoded into three characters.

I have snippets for commit messages, PR descriptions, scaffolding prompts. Each compresses a multi-step decision into one expansion. The compound effect over hundreds of sessions is enormous.

Two setups, two philosophies

At work I use Conductor. Good for structured sessions, but performance degrades after a few hours. The fix is ugly: reboot the session and start fresh. Context window management is a real constraint.

Personal projects are different. Terminal inside Zed running Claude Code. Yolo to main. No staging branches, no PR reviews, no ceremony. If it works, it ships. If it breaks, I fix it.

Work needs coordination, auditability, collaboration. Personal needs velocity. Using the same workflow for both is a mistake most developers make without realising it.

The thesis

Most developers invest in their editor and their language. Weeks on Neovim, debates over TypeScript versus Go. They will not spend an afternoon wiring up Tailscale.

The glue layer is the most underinvested part of your stack. How you access your tools. How you trigger your workflows. How you compose your systems. That is where the biggest gains hide, and almost nobody works on it.

Treat your setup as a product. Your setup has users. You, every day, for years. A snippet that saves thirty seconds saves hours a month. Mobile SSH lets you act on an idea instead of waiting until you are back at your desk.

Wire your OS. The tools are there. The glue is the work nobody wants to do, and the work that matters most.