Rohan Paul 转引 Atomic Bot 的对比实验:在 GLM 5.3 上用四个提示词让 OpenClaw 2.0 与 Hermes Agent 生成以 OpenClaw 吉祥物为主角的电影场景,OpenClaw 2.0 消耗约 2.1M tokens、约 $4.5、10 次自修复,Hermes Agent 消耗约 2.9M tokens、约 $4、20 次自修复。
OpenClaw 2.0 vs Hermes experiment by @atomicbot_ai is a good example of why the model alone tells you very little about agent performance.
Outputs:
OpenClaw 2.0: ~2.1M tokens, ~$4.5, 10 self-fixes
Hermes Agent: ~2.9M tokens, ~$4, 20 self-fixes
The difference was in how they checked themselves.
Atomic Bot lets you run AI agents in the cloud without managing the setup yourself.
In this experiment
- OpenClaw screenshotted frames at specific timestamps, counted pixels, then corrected visual errors such as an inverted coat-tail direction.
- Hermes went further and created its own render-checking setup, measuring frame timing, testing whether loop seams were visible, and auditing scenes against the original spec.
That extra ~800K tokens was largely verification work.
We usually talk about agent tokens as inference cost.
This run is a nice reminder that some of those tokens are effectively a QA budget. Once agents can generate their own checks, the important question becomes how much compute you want them spending proving their work before returning it.
OpenClaw 2.0 is available on Atomic Bot! We ran a battle: OpenClaw 2.0 vs Hermes Agent on GLM 5.3. Four prompts: movie scenes with the OpenClaw mascot in the lead role. Outputs: OpenClaw 2.0: ~2.1M tokens, ~$4.5, 10 self-fixes Hermes Agent: ~2.9M tokens, ~$4, 20 self-fixes OpenClaw screenshotted its own frames at exact timestamps, counted pixels to check its work, and filed fixes like "coat tail whip direction was inverted". Hermes went further and built itself a render harness: it measured frame times, checked the loop seam was invisible, and audited every scene against the spec before we ever opened it. That double-checking is where its extra tokens went. Run OpenClaw 2.0 in the cloud via Atomic Bot in one click!在 X 查看被引用的帖子
来源:Rohan Paul · x.com