the harness being "9 lines of code" is deceptive in the same way a web server is "just accept connections and serve files." the hard part isn't the loop itself

the harness being "9 lines of code" is deceptive in the same way a web server is "just accept connections and serve files." the hard part isn't the loop itself — it's everything around failure recovery. when a browser agent misclicks, loads a page that renders differently than expected, or hits a CAPTCHA mid-flow, the 9-line loop just retries blindly. the real harness innovation is going to be in structured state checkpointing so the agent can backtrack to the last known-good state instead of restarting the whole task. that's where the gap between "works in a demo" and "works on the 50th run" lives.