how retweeted
干的像沙漠般的一篇,关于 RL Terms.
RL 术语很多,且不好理解,例如:
policy, state, action
rewardreturn, value, advantage
baseline, TD error, GAE
clipping, KL
这篇用一个例子把 RL 的术语写给 LLM 读者 (依然太干了,RL 真的很难写得生动有趣)
how retweeted
daily reading guys
arxiv.org/abs/2610.31867
おい、始まったな!!!!!!
「モデル内部に存在する知識の非対称性を活かして学習信号に応用すると、強力な外部教師に依存することなく、基盤モデルの事後学習が可能となる」
arxiv.org/abs/2610.32770
how retweeted
The complete reasoning-from-scratch video series is now up (and linked) here: magazine.sebastianraschka.co…
(Taking a short break but will be back with LLM model and research updates in November!)
how retweeted
初来乍到,有没有大哥指个明路,
@huangguodrama 和@huangguoai
哪个是真主?两个账号的每个视频的流量差了快三倍!
官网到底是
huangguoai.com 还是 huangguo.com?
how retweeted
世界上最顶级的几个 AI 大模型公司官方放出来的深度文章,大家一定要看,
这是 @AnthropicAI 第一次把他们内部是怎么做 Prompt 优化、Agent 评测和自动调优的底层方法论,毫无保留地全盘分享出来了,
同时在 Claude Code 的官方 Skill 里直接上线了两个神级指令:
一个叫 build-eval,一个叫 hillclimb。
一句话概括它干的事:
让 AI 在你的项目代码库里,自动建真实验收测试集,然后自己改代码、自己跑分、自己去重和防过拟合,直到把准确率拉上去、把 Token 账单砍到原来的五分之一。
做过 Agent 和重度提示词的人,应该都懂那种想砸键盘的绝望感:
改了一句 Prompt,这里好像变聪明了,那里又莫名其妙崩了;
或者自己写了几个测试用例自嗨,一上线遇到真实用户直接翻车。
以前我们调优全靠肉眼瞎试和玄学,
现在 Anthropic 直接把这套工业级的自动化调优流水线开源了。
我把这篇万字干货里的核心精髓,拆成三个最值钱的维度给大家讲透:
第一个,什么是真正能打的评测(Eval)?
Anthropic 给出了四条铁律,直接打碎了很多人的认知误区:
1. 别拿今天模型的短板去建题库:
大模型的能力表面是参差不齐的。如果你专门挑它今天答错的题去考它,你测出来的根本不是任务本身的难度,而是这个特定版本的指纹缺陷。下一代模型一出,你的题库全作废。
2. 顶尖模型在最强思考档下,跑分也必须远低于 100 分:
如果你的测试集让最强模型轻松拿满分,说明题目太简单,你根本测不出后续改动到底是变好了还是变差了。
3. 裁判优先用程序,其次才是大模型:
能用代码跑单元测试、校验 JSON Schema 的,坚决不用大模型当裁判;必须用大模型当裁判时,不要打 1 到 5 分这种模糊分数,而是写成可逐条核对的事实验证清单,或者做盲测 A/B 对比。
4. 必须能区分真变好和随机波动:
如果跑分每次都不一样,说明题目有歧义,或者环境残留了上次测试的文件让 AI 抄了近道。
第二个,神级指令 `/claude-api build-eval`
你在终端里敲下这行命令,Claude 会像个资深架构师一样采访你,在你的代码库里现场搭评测系统:
先抽你生产环境的真实对话记录,再翻 Bug 报告和工单,最后才补少量合成数据。
搞定后直接在本地生成一个极简的可视化网页,把每个测试用例、评分理由、调用链路 Trace 摆在你面前,你点个确认,基线就立住了。
第三个,全自动刷分爬坡 `/claude-api hillclimb`
这是整篇文章最炸裂的部分。
有了评测集之后,你只要告诉它你的目标是提高性能还是降低成本,它就会自动把数据切成训练集和测试集,开始自动迭代:
每次只改一个最小补丁,绝不大拆大改;
如果训练集分数涨了,但独立的测试集没动,它立刻判定为过拟合,秒级回滚;
如果改动有退步,立刻撤销重来;
只有训练集和测试集双双上涨,这个改动才会被正式保留下来。
当跑分卡住两三轮不涨的时候,它不会瞎猜,而是停下来把所有失败用例拉个清单做归因分析:到底是指南写漏了,还是裁判自己判错了。
官方在文章里放了两个真实实测战报,数据非常硬核:
第一个案例:客服 Agent 极限降本
原本用 Opus 4.8 跑高思考档,准确率 74.4%,单次成本 4.6 美分。
跑完 hillclimb 后,系统自动帮它删除了冗余的思维链和冲突规则,把模型换成低思考档的 Sonnet 5,
最终在未见过的测试集上,准确率从 78.6% 飙升到了 90.5%,而单次成本直接降到了 1 美分。
准确率大涨的同时,账单直接砍掉了近 80%。
第二个案例:修复 AI 脑子里的旧时代记忆
他们在优化官方 claude-api 技能时,发现评分一直卡在 77 分。
AI 复盘后发现:模型本身其实懂新接口,但由于预训练时期的习惯,总是下意识去写老旧废弃的 API 格式。
于是自动在规则最上方补了一张新旧 API 对照表,准确率瞬间冲到了 88%。
过去我们做 AI 应用,90% 的精力都在当人肉测试员和 Prompt 缝合怪;
现在顶尖大厂的解法是把玄学变成工程:用真实的业务数据立住标尺,剩下的调优和降本,让 AI 坐在工位上自己给自己爬坡。
这套工具已经集成在 Claude Code 的官方技能库里了,终端里装上 claude-api 就能跑。
做 Agent、写提示词、或者被 API 账单卡脖子的兄弟,强烈建议去啃一遍原文。
你们平时在业务里调优 Prompt,最头疼的是改完后测不准,还是跑分很高上线就翻车?评论区交流交流~
Claude can now help you build evaluations and hillclimb on them.
In this article, we share guidance on eval design & skills that Claude Code can use to improve your applications.
claude.dev/blog/automating-e…
😲简直了!基于 Kimi K3 后训练,性能持平甚至局部反超,token 直接砍掉 40% !
关键要点:
🔹Ember-1 由 Fireworks Research 在开源 Kimi K3 上做后训练,专门治想太多
🔹Terminal-Bench 2.1:Ember-1 82.0 vs Kimi K3 80.9,质量不降反升
🔹生产 A/B(真实 coding 流量):推理 token ↓71%,总 token ↓39%,成功率几乎不变(0.753 vs 0.751)
🔹核心方法:用真实 agent 循环做 RL,教模型分清「改答案的思考」和「原地打转的废话」
🔹痛点直击:推理模型输出里经常 90%+ 都是 thinking,agent 多步循环会指数级烧钱
🔹Cline 已上线,桌面端能明显感觉思考变快、更干净
推理提供商自己下场给开源权重做效率后训练,这条路很对。Agent 时代,省 token = 省钱 + 更快闭环。
#Ember1 #KimiK3 #FireworksAI #Cline #AIAgent #TokenEfficiency #CodingAgent
Ember-1 by the Fireworks Research team is built on Kimi K3, and uses ~40% fewer tokens while achieving the same performance on benchmarks.
This was accomplished by post-training K3 to think less repetitively.
Reasoning models spend most of their output tokens (sometimes 90%+) on thinking before they answer, which gets expensive in agentic loops where the model tends to re-think the same thoughts on every step.
Fireworks RL trained on real agentic coding task loops to teach the model which reasoning actually changes the answer vs which is just looping.
In a live A/B test on coding traffic, Ember-1 used 71% fewer reasoning tokens and 39% fewer total tokens than K3 at the same success rate.
how retweeted
A little Ember-1 tl;dr.
Seems like a great model!
(Was recently asked on a podcast, given $ xx million, what's the best way to develop a frontier LLM today? My recommendation was: start with an existing one and spend that budget on post-training. Great example here.)
how retweeted
这篇应该是这几天全网把 Jev 讲得最透彻、认知穿透力最强的一篇技术图解长文了,墙裂推荐!!
过去三年我们几乎把生成式大模型当成了手里的万能锤子, 哪怕面对一个最简单的单选判断, 也要硬生生调一次几毛钱的通用大模型。
技术大牛 @akshay_pachaar 刚发出的这篇长文直接扯掉了这层遮羞布: 一个连一句完整对话都说不出来、甚至不会写一行代码的模型, 为什么刚上线就把全网架构师看燃了? 因为不能生成长文本, 恰恰是它最可怕的工程杀手锏。
绝大多数企业软件从来不需要另一个陪人闲聊的聊天框。
一个复杂的智能体在后台跑起来, 往往需要做成千上万次细碎的边界判断: 这张工单紧急吗、该挑哪个模型处理、这条命令有没有危险。
传统大模型的致命死穴是自回归生成。
哪怕最终答案只有一个单词, 它也必须在云端一个字一个字往外吐 Token, 遇到 JSON 格式错误还要重试。
调专做强类型决策的 Jev 之后, 所有的判断逻辑全部变成了一组确定的输入状态与候选问题, 输入百万 Token 仅四分钱且输出完全免单, 官方测算下延迟直接压进几十毫秒, 成本最高被砍去了 400 倍。
更耐人寻味的是它对幻觉的重新定义。
很多人鼓吹它彻底消灭了幻觉, Akshay 极为冷峻地指出了真相: 它只是在格式上百分之百免疫幻觉, 绝不可能吐出未定义的选项或者破损的文本, 但它依然可能在合法选项里选出错误答案。
这正是这套架构最值钱的地方: 它不仅交出单选结果, 还给出一整套精确校准的置信度分布。
开发者在代码里终于能写出极度理性的防线: 高置信度直接自动放行, 中置信度唤醒大模型二次复核, 低置信度无缝移交人工。
它在智能体里最绝的三个卡位, 彻底把大小脑分工跑通了: 最上游充当路由器, 替请求分流最便宜的模型; 中游充当执行闸门, 在执行高危终端命令前一秒完成风控拦截; 下游充当质检员, 监督复杂任务到底有没有真正跑通。
以前是软件迁就大模型的自回归废话, 从今天起是大模型适配工业软件的确定性分支。
如果要在你手头的系统里加一层百毫秒的语义决策, 你最想先用它替换掉哪次昂贵的大模型调用?
我先说,那些为了判断用户意图动不动就要等三秒的慢路由, 早就该换成这种纯粹的语义开关了。
三种原生决策原语的调用代码与七步安全落地法则, 我整理好放评论区了
how retweeted
Damn,三天前大家还在争论哪家大模型写代码更便宜, 今天老黄@JensenHuang 和@nvidia 英伟达直接掀桌子了: 问题根本不在模型, 在你的脚手架太蠢了。
英伟达与 MIT 团队公开了全新架构 SoL-Pi, 放弃人工打补丁, 让算法自己演化出四套运行时机制。
不仅在 GPT-5.6 Sol 和 Opus 5 上守住了评测水准, 更把 API 成本直接削去三分之一。
那些天天盯着大模型降价、却任由 Agent 脚手架疯狂烧钱的团队, 建议把这篇论文打印出来贴在工位上。
英伟达实验室开源的SoL-Pi 论文,可以说是做了一件全行业早就该做的事: 用自动演化系统重新锻造 Agent 运行脚手架。
在 51 个真实编程任务的严苛评测中, 面对 GPT-5.6 Sol 和 Claude Opus 5 这种巨无霸, 任务得分毫发无损, 但直接把 Token 消耗腰斩了 49%, 每跑一小时就能从 API 账单里直接省出 8.75 到 13.50 美元。
很多团队以前做智能体全靠工程师人肉写死调度逻辑, 试几个用例就自以为调好了, 跑进几十步的复杂长任务里, 臃肿的上下文几分钟就能把账单干爆、把模型智商撑死。
英伟达这次最聪明的一步, 是彻底放弃了人类手工调优。
他们把脚手架扔进多个不同的代码环境里, 让系统开启自动化研究循环, 像自然选择一样让无数机制自我对抗淘汰, 最终只有四个物理机制活了下来。
首先颠覆的是执行节奏。
以前 Agent 走一步看一步, 调一次工具往返一次, 动作融合机制直接把连贯动作在端侧合并批处理, 砍掉了一大半网络和上下文震荡。
然后是给运行中的上下文无损脱水。
它不是等上下文满了再调大模型写假大空的摘要, 而是在任务行进中对观察结果进行重组打包, 并在委托阅读长文件时强制保留证据行, 既把整个 API 成本砍掉整整三分之一, 又死死守住了关键代码细节不被遗忘。
以前是工程师凭直觉给 Agent 编死板的笼子, 从今天起是算法在残酷淘汰中自己进化出最精密的骨骼。
如果你的代码 Agent 每小时也能凭空省下十几美元, 你会选择把省下来的钱用来多跑十倍的并发测试, 还是换更大参数的模型? 我先说, 肯定无脑拉满并发, 把原本舍不得跑的全量回归测到爽。
开源代码、论文地址和这套四机制的详细对照表, 我整理好放在一楼了。
清华大学和无问芯穹等团队刚刚开源了一篇注定载入史册的重磅论文(已收录于 ICLR 2026,代码已开源):
他们彻底打破了所有多智能体(Multi-Agent)系统的底层范式——
大型语言模型之间,从今天起可以彻底不通过人类文字进行直接交流了!
这项被称为 C2C(Cache-to-Cache,缓存到缓存)的技术,
开篇就指出了全网 Agent 协同里最愚蠢、也最昂贵的一个死穴:
为什么两个跑在同一台服务器里的超级 AI,交流时非要像人类一样,
把脑子里极其丰富的高维思考,硬生生压缩成一个个英文或中文单词打给对方看?
现有多 Agent 协同的痛苦,做过工程的人都懂:
模型 A 思考完,必须经历极其漫长、吃显存带宽的逐字解码(Decode),慢吞吞吐出一大堆文字;
模型 B 拿到这堆文字,再重新过一遍分词和前缀计算。
这一来一回,不仅丢失了海量微观的语义细节,更造成了毁灭级的延迟和 Token 账单!
清华团队这次做了一件极其惊艳的体系化反叛——C2C 脑电波直连:
1️⃣ 彻底消灭中间文本,直接做“思维投影”:
模型 A 算完后,根本不生成任何文字,
系统直接用一个轻量级神经网络(Neural Fuser),把模型 A 的注意力记忆(KV-Cache)通过高维空间旋转和对齐,直接嫁接、融进模型 B 的 KV-Cache 脑内!
这相当于人类交流跳过了声带和耳朵,直接把我的记忆切片瞬间印进你的大脑;
2️⃣ 可学习的智能门控(Gate 机制):
不同模型的网络层数和结构各不相同,直接硬灌肯定会神经错乱。
论文设计了一套精妙的可学习门控:
大模型会自己动态感知,精确挑选哪些关键层吸收外部缓存的增益最高,哪一层该保持独立思考,毫秒级自适应配平;
3️⃣ 极其残暴的工业基准成绩:
• 彻底消灭中间所有的文本解码等待,推理速度直接飙升 2.0 到 2.5 倍;
• 综合问答准确率比单模型最高暴涨 14.2%;
• 最狠的是:它的表现比传统用文字互相聊天的 Agent 团队,还要高出整整 5%!
因为在直接的语义融合下,原本会被文字丢弃的逻辑细微特征,全部被完整保真保留了。
这篇论文最刺痛人的一层哲学启示在于:
人类一直自豪地以为,自然语言是这个星球上传递智慧最完美的介质;
但在机器与机器的交互世界里,人类语言不过是一道充满歧义、极其拥挤的低速单行道。
当两个模型不再需要通过文字向对方妥协,
它们正在绕过人类的喉咙,
在冰冷的显存带宽之间,编织出一座全人类根本听不见、却快得不可思议的超高速无声神经网络。
how retweeted
A Primer paper about how reasoning models improve after training
Shows that better reasoning models depend less on raw data size and more on checkable training evidence.
reasoning data is NOT simple question-and-answer pairs. The useful part is often the feedback that says why an answer, step, tool action, or full attempt was good or bad.
A prompt and a response tell you what a model said, but not why that answer became learnable, which judge blessed it, which failures were hidden, or whether the skill was already inside the base model.
The core idea is to describe each training example as a record that includes the task, the model’s behavior, the checking signal, and metadata about where it came from.
The authors sort reasoning data by how it can be checked, such as exact rule-based checks for math and code, environment checks for agents using tools, and human or model judgments when no exact checker exists.
They also explain why common assumptions fail, because long reasoning traces may be fake, harder examples may be useless for some models, and larger datasets may still miss important coverage.
The key point is that agent data should preserve mess: failed actions, retries, recoveries, state differences, and terminal checks, because that is where learning signal often lives.
----
Link – arxiv. org/abs/2606.02113
Title: "A Primer in Post-Training Reasoning Data: What They Know About How It Works"
This SkillOpt paper from Microsoft is a must-read!
(bookmark it)
I was a bit skeptical of the results reported in the paper when I shared it a few days ago.
However, I managed to integrate it into my agent orchestrator and ran a few experiments.
The results are mindblowing.
Essentially, all my agent skills now have a proper testing framework and a way to self-evolve. I have started to improve all my agent skills with this.
One exciting result was when I applied it to my paper-figure-extraction skill, which requires an agent to do multimodal analysis. In particular, it improved quality by +20 points (0.73 → 0.93). I went to see the extracted tables and figures, and I was absolutely stunned by how much better my skill got at the task.
Self-improving AI is in the early days, but I think this work is a clear example of the current ability of agents to self-improve.
In this case, it was skills, but it's not hard to imagine how this scales to optimizing agent patterns, tool use, context engineering efforts, agentic search, workflows, evals, and even the harness itself. I already started with a few of these ideas inspired by SkillOpt.
Stay tuned!
how retweeted
Have you ever wondered how to formalize what an agentic system actually is? Meaning where they fit in the book of ML and how to explain/predict their performance?
We argue here, agents can be seen as boosting reasoning models!
arxiv.org/abs/2605.14163
how retweeted
Sharing our latest work on offline self-distillation:
📑 Self-Policy Distillation (SPD): arxiv.org/pdf/2605.22675
Self-distillation methods often need some external scoring signal. But these signals are becoming harder to source for the strongest frontier models, which are themselves already the "teacher."
Activation steering, on a separate track, has shown that intervening on a model's hidden activations at inference time can change behavior without updating weights. Most work applies this to behavioral control — refusal, sycophancy, honesty — using directions extracted by contrasting activations with and without the target behavior.
SPD builds on these two threads for capability transfer.
It steers self-generated training data by projecting KV activations into a capability-selective subspace, then fine-tunes on the resulting outputs with plain next-token loss.
Concretely, there are two phases.
First, on a small calibration set (50 examples is enough), SPD computes a loss only on the tokens that determine task success — assert test cases in code, the final numeric answer in math, the option letter after "Answer:", etc.
Backpropagating that loss to the K and V activations, then applying SVD, gives a low-rank activation subspace that captures directions most important for correctness.
Second, SPD generates self-training data under that subspace. At each decoding step, the K and V activations are projected into the subspace, biasing samples toward capability-relevant directions.
The projection is then removed, and the original model is fine-tuned on the resulting prompt–completion pairs with standard next-token loss.
Across code, math, and multiple-choice QA — MBPP, CodeAlpaca, GSM8K, SVAMP, MMLU, and BBH — on Qwen2.5-0.5B/7B/14B, Qwen3-4B, and Llama-3.1-8B, SPD achieves up to 13% improvement over other self-distillation baselines without external signals.
Furthermore, the out-of-domain transfer is where projection-based steering shows it is reaching deeper into model capability.
A KV subspace extracted from QA gradients alone yields +136% relative improvement on GSM8K and +24% on MBPP.
It shows that whatever direction the SVD is picking up isn't multiple-choice-specific (e.g., format).
It's something more general in the reasoning and problem-solving space.
As models outgrow their graders, SPD can be especially useful when stronger teachers are unavailable or expensive, which is also the case as LLMs land into more specialized verticals.
GitHub 上一个叫《Learn Harness Engineering》的开源课程最近上了 Hacker News 首页(155 分、5.1k stars),
主题是 AI coding agent 的可靠性工程——也就是 OpenAI 和 Anthropic 最近几个月一直在讲的 harness engineering。
github.com/walkinglabs/learn…
作者是清华 SIGS 的开源团队 walkinglabs,课程内容 12 节 lecture + 6 个实战项目,全部围绕同一个压轴项目(一个 Electron 知识库 app),目前已经有 13 种语言版本。
核心讲的是这几条:
1、Harness Engineering 是新概念但绝不只是营销:
OpenAI 2026 年 2 月在 Codex 官方博客正式提出,Anthropic 同期发了两篇配套工程文章。这门课是把这两家分散的工程内容系统整理成中文可读的体系,不是发明新东西;
2、核心论点是模型不是问题,环境才是:
Anthropic 自己跑过一个对照实验,同样的 Opus 4.5、同样的提示词("做一个 2D retro 游戏编辑器"),没 harness 花 $9 跑 20 分钟出不来;有完整 harness(planner + generator + evaluator)花 $200 跑 6 小时跑出来一个能玩的游戏。差距不在模型,在环境;
3、Harness 的 5 个子系统:
Instructions(agent 看什么)、State(已经做了什么)、Verification(怎么算完成)、Scope(一次只做一个 feature)、Lifecycle(会话起手和收尾);
4、最小起手 4 个文件:
AGENTS.md(操作手册)、init.sh(每次起手跑的环境检查脚本)、feature_list.json(机器可读的功能边界)、claude-progress.md(会话之间的进度交接)。这 4 个文件直接丢进你现有代码库就能用,不用读完 12 节课;
5、为什么 agent 总是搞砸(课程反复回答的几个问题):
一次想做 3 件事但 3 件都只做一半;说"done"但其实 test 跑不过;跨会话完全没有记忆,这次写到一半下次重头来;没有验证流水线就没有真完成(只有 test pass + lint pass + e2e pass 三件齐了才算);
6、6 个项目渐进式演进:
P01 prompt-only vs rules-first 对照看差距、P02 把代码库改成 agent 能读的结构、P03 跨会话续接、P04 加运行时反馈控制范围、P05 让 agent 自验、P06 完整 harness 加可观测性;
7、压轴项目是个 Electron 知识库 app:
每个项目的答案就是下一个项目的起手代码——app 在演进,你的 harness 技能也在演进;
总结:
"AI agent 工程师"这个角色正在从"会写提示词的人"变成"会搭 harness 的人"。
这门课本身不算硬核,但它把 OpenAI 和 Anthropic 两家工程博客分散的内容系统整理成了中文索引,对中文圈想入门这个方向的人来说,能省下读 5 篇英文工程博客的时间。
Bullish on Demis and the DeepMind team.
Beautiful result from GoogleDeepMind:
(this one has been quite useful to me) Its an ablation on how the chat template can be an extraction plane on open-weight models. Prompting with just the template and the model regurgitates its own SFT/RL training. “distillation” quietly carries a teacher's alignment data with it.
arxiv.org/abs/2510.18554
// LLMs Improving LLMs //
Interesting progress the past of couple of weeks around self-improving AI agents.
If autoresearch was interesting, you will like this read.
(bookmark it)
We've been hand-tuning test-time scaling for a year. This work asks what happens when you let an LLM search the space instead.
The paper introduces AutoTTS, a framework that reframes the human role: instead of designing branching, pruning, and stopping heuristics directly, you construct a discovery environment where TTS strategies can be searched automatically. They formulate width–depth TTS as controller synthesis over pre-collected reasoning trajectories and probe signals, so candidate controllers can be evaluated cheaply without repeated LLM calls.
Two design choices carry the search. Beta parameterization makes the control space tractable. Fine-grained execution-trace feedback tells the explorer LLM why a candidate failed, not just that it did.
On math reasoning benchmarks, the discovered controllers beat strong hand-designed baselines on the accuracy–cost Pareto frontier and generalize zero-shot to held-out benchmarks and model scales.
Entire discovery cost: $39.9 and 160 minutes.
Why it matters:
The era of researchers hand-crafting CoT, best-of-N, and self-consistency recipes is on a clock. Once the search loop is cheap enough, TTS becomes another thing LLMs do for themselves.
Paper: arxiv.org/abs/2605.08083
Learn to build effective AI agents in our academy: academy.dair.ai/


















































