People freaking out over my AI spend. What nobody sees: Part of what excites me so much about working on OpenClaw is that I'm trying to answer the question: How would we build software in the future if tokens don't matter? We constant run ~100 codex in the cloud, reviewing every PR, every issue. If a fix on main lands, @clawsweeper will eventually find that 6 month old issue and close it with an exact reference. We run codex on every commit to review for security issues (as it's far too easy to miss). We run codex to de-duplicate issues and find clusters and send reports for the most pressing issues. We have agents that can recreate complex setups, spin up ephemeral machines, log into e.g. Telegram, make a video and post before/after fix on the PR. There's codex that watch new issues and - if it fits our documented vision well, automatically create a PR of it. (that then another codex reviews) We have codex running that scans comments for spam and blocks people. We have codex instances running that verify performance benchmarks and report regressions into Discord. We have agents that listen on our meetings and proactively start work, e.g. create PRs when we discuss new features while we discuss them. We build to split all our projects into functional units to review and find bugs and regresssions. We do the same split for security with Vercel's deepsec and Codex Security to find regressions and vulnerabilities. All that automation allows us to run this project extremely lean.
大家都在对我的 AI 开销大惊小怪。但没人看到的是：让我对参与 OpenClaw 如此兴奋的部分原因，是我在尝试回答这样一个问题：如果 token 不再重要，未来我们会如何构建软件？我们持续在云端运行大约 100 个 codex，审查每一个 PR、每一个 issue。只要 main 上落地了一个修复，@clawsweeper 最终就会找到那个 6 个月前的旧 issue，并用精确引用把它关闭。我们在每一次 commit 上都运行 codex 来审查安全问题（因为这类问题实在太容易漏掉）。我们还运行 codex 来给 issue 去重、发现问题簇，并为最紧急的问题发送报告。我们有一些 agent（智能体）能够复现复杂环境、拉起临时机器、登录例如 Telegram、录制视频，并把修复前/修复后的结果发到 PR 里。还有一些 codex 会监控新 issue——如果它很符合我们文档化的愿景，就会自动为它创建一个 PR。（然后再由另一个 codex 审查。）我们还运行 codex 来扫描评论中的垃圾信息并封禁用户。我们也运行多个 codex 实例来验证性能 benchmark，并把性能回退报告到 Discord。我们有一些 agent 会监听会议，并主动开始工作，比如当我们在讨论新功能时，它们会一边听一边创建 PR。我们构建了一套机制，把所有项目拆分成多个功能单元，以便审查并发现 bug 和回归。我们也为安全做了同样的拆分，结合 Vercel 的 deepsec 和 Codex Security 来发现回归和漏洞。所有这些自动化，让我们能以极度精简的方式运行这个项目。
Been using @sveltejs for a few projects lately, it's quite a nice alternative to React, fewer gotchas and complexity and Codex handles it really well.
最近我在几个项目里一直在用 @sveltejs，它是 React 的一个相当不错的替代方案，坑更少、复杂度更低，而且 Codex 对它的处理也非常好。
🩹 clawpatch 0.1.0 is live: Clawpatch maps codebases into semantic feature slices, reviews them for bugs and quality issues, and records explicit fix attempts with validation. You'll be surprised how much this will find. npm install -g clawpatch
🩹 clawpatch 0.1.0 已上线：Clawpatch 会把代码库映射成按语义划分的功能切片，审查其中的 bug 和质量问题，并记录带有验证结果的明确修复尝试。你会惊讶于它能发现多少问题。npm install -g clawpatch