#编码

昨天我老婆问我 App Store 怎么付费，看了一下才知道她要给儿子买一个打字 App，收费 128 块。。 这。。小孩和女人钱这么好赚？？ 我说等我半个小时，打开 Codex，把打字游戏的需求输入进去，一个 Goal 跑起来，20 分钟就做好部署到 ChatGPT Sites 了。花了几分钟看了一遍，还不错，顺手再加了一个实时拍摄人像，让头像作为游戏主角的功能，30 分钟准时交活儿。 效果怎么样呢？我第一版做了 36 关，儿子一连玩了 18 关 😁😁😁，我边看他玩，边看有什么问题，边让 Codex 改，顺便增加了几十关，和无限模式。。 以后儿子再有什么想玩但花钱的游戏和应用，自己做就行了，大家感兴趣可以看这: https://keyboard-island-doudou.groovy-river-7567.chatgpt.site

MiniMax M3.1 Flash (aka Space Bunny) is now live and FREE in Command Code for limited time! · 1M token context window · Frontier level coding performance · Available all plans, all subscribers

MiniMax M3.1 Flash, aka Space Bunny, is now available on GMI Built for coding, agentic workflows, and computer use 70% lower agentic task costs, 73.7% on DeepSWE v1.1, 82% on CyberGym Run it now 👇

MiniMax M3.1 Flash goes toe-to-toe with Opus and GPT on coding at ~25x lower cost. This was the model behind Space Bunny, the stealth model that’s been topping usage leaderboards recently. Free in Cline now!

由 @AIatMeta 推出的 Muse Wonder (Max) 已进入 Code Arena：WebDev 以 1651 分位列第 15，Text Arena 以 1513 分位列第 2！ 在 Code Arena：WebDev 中，Muse Wonder (Max) 以 1651 分位列第 15。这一结果略低于以 1659 分位列第 12 的 Muse Spark 1.3 (Max)，与以 1655 分位列第 14 的 Kimi K3 (Max) 相差 4 分以内，并比以 1640 分位列第 16 的 Grok 4.7 (xHigh) 高 11 分。 此次发布在 Text Arena 中相较过去的 Muse 模型有显著提升。与以 1494 分位列第 11 的 Muse Spark 1.3 (Max) 相比，Muse Wonder (Max) 提升了 +19 分并上升 9 位至第 2。它落后于以 1525 分排名第 1 的 Gemini 4 Argon (High) 12 分。 祝贺 @AIatMeta 团队发布这一版本！

MiniMax M3.1 Flash：太空级性能 + 兔子级速度 🚀🐰 没错，Space Bunny——曾以 200T+ tokens 登顶全球排行榜——正是 M3.1 Flash 的早期版本。 💰重新定义智能体 AI 的性能经济学。M3.1 Flash 在 Cowork（Automation-Bench：62%；ALE：30%）、编程（DeepSWE：74%）和视觉推理（BabyVision：91%）等关键任务上达到前沿级智能水平，成本仅为 M3 的 1/3，速度提升 3 倍。 API 定价（统一费率）：每 1M 输入/输出 tokens 分别为 $0.15 / $0.60，缓存读取为 $0.015 / 1M tokens。 模型权重将于 10 月 23 日发布。 API：http://platform.minimax.io M Plan：https://www.minimax.io/m-plan MiniMax Code 桌面版：https://agent.minimax.io/download

MiniMax M3.1 Flash：太空级性能 + 兔子级速度 🚀🐰 没错，Space Bunny——曾以 200T+ tokens 登顶全球排行榜——正是 M3.1 Flash 的早期版本。 💰重新定义智能体 AI 的性能经济学。M3.1 Flash 在 Cowork（Automation-Bench：62%；ALE：30%）、编程（DeepSWE：74%）和视觉推理（BabyVision：91%）等关键任务上达到前沿级智能水平，成本仅为 M3 的 1/3，速度提升 3 倍。 API 定价（统一费率）：每 1M 输入/输出 tokens 分别为 $0.15 / $0.60，缓存读取为 $0.015 / 1M tokens。 模型权重将于 10 月 23 日发布。 API：http://platform.minimax.io M Plan：https://www.minimax.io/m-plan MiniMax Code 桌面版：https://agent.minimax.io/download

Welcome back. Space Bunny. 🚀 MiniMax-M3.1-Flash is coming.

Give your agent a way to verify its work. This can dramatically improve the quality of output. With this process in place, Claude Code was able to write 90%+ of its code itself. When generating software at a faster rate than you can review it, the bottleneck shifts to proving that it works. @bcherny and team invested enough in verification, we've been able to move fast while maintaining stability. Code reviews aren't going away, but you need to think of it differently. One human reading through line-by-line is no longer going to work as a gate, it needs to evolve into a multi-layered verification system, built with fast deterministic feedback loops for your agents. This is where e2e tests, feature maps (as @poteto has been advocating), property tests and multi-agent adversarial reviews come in. These all provide opportunities to catch errors early and fix them before things get out of hand. You don't have enough eyeballs for the amount of code being written so your focus needs to be on product intent, risk assessment and evaluating evidence rather than reviewing code. Delegate the code checking work to your automated tests, scale your approvals based on risk, and turn your test failures into living evaluations. This approach helps maintain speed without losing reliability. Let the agents do what they do best and let you focus on what makes you irreplaceable: judgement, direction, and ownership. We tried to capture how we handle code review and verification in this writeup. Hopefully it's helpful.

pstack v0.15.27 ships with a new skill /create-formal-verification-skill! it's still in beta, and similar to /create-verification-skill, this is a meta-skill that creates a new skill and formal verification suite based on the characteristics you want to verify. for example, you may want to model state machines and systems with concurrency using TLA+, or use kani in rust to check for undefined behavior. if you're new to formal verification, think of it as mathematically proving properties and invariants (something that must always be true) or "laws" of your system. usually, this means modeling your programs in a separate language like with TLA+ and then running the solver on that spec. newer approaches like with kani and @bendlang take a different approach where there is no separate language: you write kani in rust, and bend in bend (it's also a programming language, and the proofs are written as laws and expressed in its type system). historically formal verification never reached mainstream status because of the difficulty in modeling and writing proofs. it's quite difficult to model your business requirements and keep them in sync! but i expect that we will see more innovation in formal verification in the future as being able to formally verifiy that the code does what you intended gives your agents superpowers in writing correct software. in the meantime though, i've been experimenting with modeling our code with TLA+ and have already found several bugs with the skill created by /create-formal-verification-skill. try it out and let me know how it goes!

A middleware engineer in South Korea wrote to me, seeking help on what to do now that their manager is "blinded by GenAI hype" and set an "AI token usage" KPI. This eng is using v little AI, so manager is poking them to use more. My response: your manager is trying to help you