## On Loopcraft One might argue the entire game of the next century is to be able to stack loops as effectively as possible. In the early days of each phase, it will be valuable to know when to go **DOWN** a loop when things go wrong (for reliability)… but it will probably be more valuable to know how to go **UP** a loop as models improve (for leverage). If you don’t figure out how to do this, don’t be salty when you lose to those that do.
## 关于 Loopcraft 有人可能会说，下个世纪的整个游戏，就是要尽可能高效地堆叠 loops（循环）。在每个阶段的早期，当事情出错时，知道什么时候沿着 loop **向下**走会很有价值（为了 reliability，可靠性）……但随着 models（模型）变得更强，知道如何沿着 loop **向上**走，大概会更有价值（为了 leverage，杠杆效应）。如果你搞不清楚该怎么做，那么当你输给那些会做的人时，也别酸。
the #1 thing that is driving me to build my own vibecoding platform rn is that none of them - and i lov vercel, cloudflare, netlify etc - none of them really close the loop for you in terms of setting you on the right path with errors and pinging you when shit fails (shit always fails) there's way too much "webmaster" infra to setup for every single project and i just want to do it once and for all, instead i'm being asked to npx posthog wizard here and npx arize skills there and it all just needs to be swallowed up into One Thing.
眼下，驱动我去自己做一个 vibecoding 平台的头号原因是：现有这些平台——而且我真的很喜欢 vercel、cloudflare、netlify 等——没有一个能真正帮你把 loop（闭环）补上，也就是说，在报错时把你引到正确路径上，并且在东西挂掉时提醒你（东西总是会挂）。每一个项目都要搭太多“webmaster”式的 infra（基础设施），而我只想一劳永逸地把这事做一次；结果现在却还要我这里 npx posthog wizard、那里 npx arize skills，这一切都应该被吞并进 One Thing。
congrats to our friends @ona_hq on joining @openai! see their talk here for alpha on what’s next for Codex 👀
恭喜我们的朋友 @ona_hq 加入 @openai！想知道 Codex 接下来会怎样，可以看看他们这场 talk，里面有一些 alpha（一手消息）👀