Back to Stories
Development

I ship changes from my phone, because I built the loop that makes the laptop optional

This website was built almost entirely from my phone. Not as a stunt, and not because phones are good development environments. Because I designed the loop that makes a laptop optional, and once that loop is solid the device stops mattering.

The loop

I send an instruction over Telegram. My agent runs on a machine at home. It reads the project, makes the change, commits to a QA branch, and pushes. The preview builds automatically. Two to three minutes later a preview URL lands on my phone. I look at it, I respond, it adjusts. When it is right, I approve the merge. Nothing reaches production without that approval.

"Simplify the menu to four items and add a stories section." That is the instruction. Not pseudocode, not a spec. Just what I want.

Why it is trustworthy and not reckless

Three things hold it together.

Context persistence. The agent already knows the project structure, the patterns, where things live. I never re-explain the codebase.

A QA gate. Nothing ships without my explicit GO. I review on my phone and merge when it is right, not before.

Governance. The agent knows what it may and may not do. It can write code and commit to the QA branch. It cannot deploy to production on its own. That boundary is written down, not assumed.

The actual work

My job is the decisions. What should this look like, how should it behave, what matters and what does not. The implementation is handled. I am not pretending the code writes itself. I designed the system that writes it, set the rules it runs under, and I review every result before it goes live. That is the work. The typing was never the work.

The honest part

It is not magic, and it is not always two minutes. When the system has a gap, a missing credential or an unconfigured redirect, the loop stalls and I have to go close that gap. Every smooth run is the payoff from an earlier rough one I fixed. The polish is invisible precisely because I already paid for it.

What it taught me

People think the headline is "built from a phone." It is not. The headline is that the gap between having an idea and seeing it live shrank from hours to minutes. At that point, where I happen to be standing stops being relevant. A street in a city or a desk at home, the system does not care, and neither do I.

Ready to build your infrastructure?

Tell me about your workflow. I'll show you what becomes possible.

Start with a conversation

Describe your current setup. I'll map out what an AI-augmented version could look like. No pitch, no commitment—just clarity.

Let's talk

Or email directly: kris@coel.ai