When you are paid to sit on your ass to review as much generated code as you can, or to create as much good code as possible given the constraints of a limited amount of tokens, sure. But when you're on your own clock, the trade-off between latency, token budget and quality shifts considerably. And when it actually is a side project (yeah, many meanings of "serious" will be out, I give you that), mobile is just awesome.

That slow trickle of back and forth that gets our intelligent machines called "toasters" in a way not predicted by Battlestar Galactica at all, that really starts shining on mobile. Hands off on terms of signing off every little detail, hands on in terms of never being too far out of the loop, keeping the unattended steps small.

I'm not sure what the problem is after rereading their post? All you need to support everything they said is a remote connection to a heirarchy of worktree-supporting sessions per project, with each having a proper scrolling feed of agent actions taken and your input box.

Sorry, I meant "on mobile apps." I'm still using a laptop. :)