HackerNews中文版

我已经密集使用 OpenClaw 大约两周了。最开始的几天让我感到兴奋。感觉我们终于接近能够实现端到端操作计算机的自主代理了。但在初期的兴奋感消退后，我开始注意到一些持续存在的问题：- 它经常在任务进行中停止响应- 执行失败时没有明确的恢复机制- 任务成功率感觉不稳定且不可预测- 长时间运行的任务会随着时间的推移而退化这让我开始怀疑当前的架构是否在根本上限制了可靠性。现在，它更像是一个“单一程序试图做所有事情”的模型。但如果我们回顾计算历史，系统只有在向操作系统类似的抽象转变时才变得真正稳健：- 事件驱动执行- 适当的故障恢复- 看门狗/心跳监测- 任务监督树- 状态持久性和可恢复性换句话说，少一些像脚本的特性，多一些像操作系统的特性。我目前的假设是，像 OpenClaw 这样的工具可能需要更深层次的重新架构——不仅仅是更好的提示或增量补丁——而是从一开始就专注于可靠性和可扩展性的系统级重新思考。我很好奇其他人的看法：这主要是一个工程成熟度的问题，会逐步修复吗？还是当前代理框架中存在更根本的架构缺口？有没有人尝试过构建更像操作系统的监督模型的代理？希望听到在这个领域工作的人的观点。

查看原文

I’ve been using OpenClaw intensively for about two weeks.The first few days were exciting. It felt like we’re finally getting closer to autonomous agents that can actually operate a computer end-to-end. But after the initial excitement faded, I started noticing some consistent issues:- It frequently stops responding mid-task- Execution fails without clear recovery- Task success rate feels inconsistent and unpredictable- Long-running tasks degrade over timeIt made me wonder whether the current architecture is fundamentally limiting reliability.Right now, it feels closer to a “single program trying to do everything” model. But if we look at the history of computing, systems only became truly robust when we moved toward operating system–like abstractions:- event-driven execution- proper failure recovery- watchdog / heartbeat monitoring- task supervision trees- state persistence and resumabilityIn other words, less like a script, more like an OS.My current hypothesis is that tools like OpenClaw might need a deeper re-architecture — not just better prompting or incremental patches — but a system-level rethink focused on reliability and scalability from day one.Curious what others think:Is this mainly an engineering maturity issue that will be fixed incrementally?Or is there a more fundamental architectural gap in current agent frameworks?Has anyone tried building agents with more OS-like supervision models?Would love to hear perspectives from people building in this space.

请问HN：OpenClaw是否需要重新架构才能使用？