The Phone Is a Valid Dev Machine
I unblocked a three-day agent from a phone while waiting for coffee, and the fix was not typing code on glass. The agent had stalled on a staging-only settings bug. Same loop from Let It Run for Days : reproduce, trace, fix, verify. The log was fine. The stop condition was fine. What it needed was a one-line decision I had been avoiding: empty string is omit, not clear. I approved the smallest…
A phone can be a valid development machine, rather than merely a tool for notifications and triage. In one instance, a three-day agent was stalled on a staging-only settings bug. The issue required a simple one-line patch, specifically setting an empty string to omit instead of clear. After approving the smallest reversible patch, the CI was quickly green, and the agent was able to continue.
The story challenges the notion that a phone is too small for real work, pointing out that the real bottleneck is the lack of a shipping system that can be accessed from any location. A phone can be used to steer agents, review evidence, unblock stalled loops, and kick off the next job, as long as the blast radius and contracts travel with you.
This approach shortens the time between a stall and a named decision, rather than diluting ownership or requiring large refactors. The mechanism to achieve this involves creating a pocket contract that outlines the goal, blast radius, evidence, and decision options that can be enforced on the phone.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
