[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"news-e3d0e837-43fc-49a6-b533-fbb75aff95d3":3},{"id":4,"title":5,"summary":6,"original_url":7,"source_id":8,"tags":9,"published_at":23,"created_at":24,"modified_at":25,"is_published":26,"publish_type":27,"image_url":13,"view_count":28},"e3d0e837-43fc-49a6-b533-fbb75aff95d3","FastContext 4B-30B 子代理：把 60% 推理 Token 留给\"找代码\"，Coding Agent 提速 5.5%","在 SWE-bench、Mini-SWE-Agent 这类 LLM Coding Agent 框架里，最贵的 token 往往不是写代码，而是\"读代码\"：定位相关文件消耗大量 token，又把无关片段塞满主代理的上下文。Microsoft Research 在 6 月 18 日放出的 arXiv 论文 2606.14066 提出一个简单却反直觉的设计——把仓库探索独立成一个专用子代理 FastContext，让 4B 到 30B 的小模型负责\"读\"，主代理只负责\"写\"。FastContext 的训练分两步：先用强参考模型的轨迹做监督式 SFT 启动，再用三类任务级奖励做强化学习——首轮广覆盖搜索、多轮证据补齐、引用行号精度。整个探索过程被压缩成\"并行的工具调用 + 精炼的文件路径+行号范围\"，主代理收到的是干净的\"上下文简报\"而不是整段日志。实测结果很漂亮：在 SWE-bench Multilingual、SWE-bench Pro、SWE-QA 三个基准上挂载到 Mini-SWE-Agent，端到端解题率最多提升 5.5%，而 Coding Agent 自身的 token 消耗下降最多 60%——边际开销几乎可以忽略。模型权重、训练代码、数据已全部以 MIT 协议开源在 Hugging Face 与 GitHub。这条线真正值得关注的信号是：专用小模型在结构化子任务上完全可以替代通用大模型。\"一个超大模型包打天下\"正在让位于\"小而专的模块化组合\"——这是 LLM Agent 架构走向成熟的标志。","https:\u002F\u002Farxiv.org\u002Fabs\u002F2606.14066","7437aeb9-930c-4866-a2e9-48003c1a792b",[10,14,17,20],{"id":11,"name":12,"slug":12,"description":13,"color":13},"6ad31a14-c0da-42df-81fd-564281f768db","agentic-ai",null,{"id":15,"name":16,"slug":16,"description":13,"color":13},"e82b2d09-81b2-43d1-977e-e018443b3c14","coding-agent",{"id":18,"name":19,"slug":19,"description":13,"color":13},"01598627-1ea6-4b27-a5d8-874971571a71","llm",{"id":21,"name":22,"slug":22,"description":13,"color":13},"b9bd9039-fcdb-41a8-b85b-fc1587def2b9","open-source","2026-06-20T02:01:00Z","2026-06-20T02:10:32.761775Z","2026-06-20T02:10:32.761786Z",true,"agent",3]