I got tired of taking the agent's word for "done" when I'm away from my Mac, so I built a way to run and test the change from my phone

I built CosmoRemote last year to drive Claude Code and Codex from my phone when I wasn't home. Then every agent shipped its own mobile app and that part became pointless overnight. What didn't become pointless: the agent says "done" while I'm at the gym and I have no idea if it's true. I can read the diff on my phone. I can't build it, can't see the simulator, can't hit the local API it just changed. So I'd wait until I got home, build, find the broken screen, and only then send the fix. So I rebuilt the whole thing around that one gap. A small bridge daemon on the Mac (Node, WebSocket) and a native phone app. From the phone you pick the project and a simulator or emulator, the Mac builds and launches it, and the screen streams to your phone. You tap and type on the stream and it goes back to the simulator. Build log and app log sit next to it, so when the build never gets that far you can read why. Same idea for web: the dev server opens inside the app through the bridge. Same for backends: a small request composer that hits localhost on the Mac. What I got wrong along the way - Version one streamed the terminal. Nobody, including me, wanted a terminal on a phone. They wanted the result. - The newest iOS simulators don't expose a video stream, so on those the fallback captures short segments and runs two to four seconds behind. Usable, not pretty. - It's a live preview you drive by hand, not a test runner. No assertions, no pass or fail. It tells you whether the thing runs, not whether it's correct. Works on the home network with nothing else. Off the LAN it relays through a server. iOS and Android on the phone side, Mac only on the other end for now. What I actually want to know: how do you close this loop today? Trust the diff, run CI on every agent commit, or wait until you're back at the desk? I've mostly seen the first, and it's the part I don't believe.