How to Keep Shipping When You Walk Away from Your Desk — Zack Proser, WorkOS

TL;DR

• 1

  Agents are no longer the bottleneck, your attention is: Proser argues that with tools like Claude Code, MCP connections, and cloud APIs, agents can loop and verify indefinitely, but human focus still degrades under load and becomes the real limiting factor.

• 2

  A tiny integration can remove huge context-switching cost: By giving Claude Code read-write access to Slack and existing access to Linear, he had it fix a sentence-case bug that mangled acronyms like SKIM and SSO, test the result in the actual blog bot flow, and return only when the bug was definitively closed.

• 3

  Voice-first coding compounds fast: Proser says he went from roughly 90 WPM typing to about 184 WPM speaking, which lets him run multiple agent workflows in parallel while someone else might still be typing their first prompt.

• 4

  Remote control changes what 'walking away' means: With Claude Code remote control enabled, he can start work on his dev machine, leave the house, and keep steering the same session from his phone over LTE, including reviewing PRs from the woods and sending design fixes back in real time.

• 5

  Verification gates are what make mobile and parallel work safe: His stack ranges from lint, build, and unit tests, to browser-based checks like "make sure login still works," to a second-agent review model similar to Anthropic's constitutional AI.

• 6

  Treat your agent chat logs like training data for your own system: Because Claude Code stores conversations locally as JSONL, Proser runs review passes over them to find where he and the model struggled, then turns those patterns into new skills, MCP tools, or workflow changes so next week runs tighter than this week.