GLM-5 · BrowseComp(GLM-5固定v2报告/模型卡;with context management),GLM-5 · 报告与固定模型卡配置,Reported score 75.9(具体成绩公布时间未确认)。见《GLM-5: from Vibe Coding to Agentic Engineering》PDF p.36;Appendix B.2 BrowseComp protocol;相关协议见附录B.2。 查看成绩条件
BrowseComp: Without context management, we retain details from the most recent 5 turns. With context management, we use the same discard-all strategy as DeepSeek-V3.2 and Kimi K2.5.
The report's section 4.2.4 describes hybrid Hierarchical Context Management (keep-recent k=5 plus discard-all at T=32k), while the appendix and HF card footnote describe the context-managed setting as the same discard-all strategy used by DeepSeek-V3.2 and Kimi K2.5. The exact final-run protocol is therefore ambiguous.
条件
The report's section 4.2.4 describes hybrid Hierarchical Context Management (keep-recent k=5 plus discard-all at T=32k), while the appendix and HF card footnote describe the context-managed setting as the same discard-all strategy used by DeepSeek-V3.2 and Kimi K2.5. The exact final-run protocol is therefore ambiguous. Retained as candidate because the official sources conflict on the context-management protocol.
Official source for BrowseComp · GLM-5固定v2报告/模型卡;with context management in GLM-5. GLM-5 · 报告与固定模型卡 · 75.9. See “GLM-5: from Vibe Coding to Agentic Engineering” at PDF p.36;Appendix B.2 BrowseComp protocol;相关协议见附录B.2. Evidence ev-gm5-glm-5-browsecomp-context-management-4.
GLM-5 · BrowseComp (GLM-5固定v2报告/模型卡;with context management), configuration GLM-5 · 报告与固定模型卡, Reported score 75.9 (exact score publication date unconfirmed). See “GLM-5: from Vibe Coding to Agentic Engineering” at PDF p.36;Appendix B.2 BrowseComp protocol;相关协议见附录B.2. View score conditions
BrowseComp: Without context management, we retain details from the most recent 5 turns. With context management, we use the same discard-all strategy as DeepSeek-V3.2 and Kimi K2.5.
The report's section 4.2.4 describes hybrid Hierarchical Context Management (keep-recent k=5 plus discard-all at T=32k), while the appendix and HF card footnote describe the context-managed setting as the same discard-all strategy used by DeepSeek-V3.2 and Kimi K2.5. The exact final-run protocol is therefore ambiguous.
Conditions
The report's section 4.2.4 describes hybrid Hierarchical Context Management (keep-recent k=5 plus discard-all at T=32k), while the appendix and HF card footnote describe the context-managed setting as the same discard-all strategy used by DeepSeek-V3.2 and Kimi K2.5. The exact final-run protocol is therefore ambiguous. Retained as candidate because the official sources conflict on the context-management protocol.