【补偿申请】ZCode 完成验证器设计缺陷导致 292 次迭代无效循环，浪费约 640M token
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue describes completion-validator behavior but names no implementation files or tests. Start by locating the completion validator and reading how it handles repeated failures and requests that need physical user action. Done means it can pause after repeated identical failures, accept an explicit report that work cannot be completed remotely, and wait for user action without continuing the loop.
Written by the indexing model from the issue text.
Description
事件概述
- 日期: 2026-10-12
- 会话迭代次数: 292
- 总 Token 使用量: ~440M
- 估计浪费 Token: ~640M
- 模型: glm-5.2
问题描述
在执行教学思维改造计划时，遇到 iPad 真机测试阻塞（需要物理操作解锁设备），ZCode 的完成验证器无法识别"无法远程解决"的情况，导致 292 次迭代重复相同的无效操作。
浪费明细
| 类别 | 次数 | Token/次 | 总 Token |
|---|---|---|---|
| BFU 状态重复轮询 | 60 | 3M | 180M |
| Automation timeout 重复 | 10 | 3M | 30M |
| 证书信任重置重复 | 6 | 3M | 18M |
| 后端不可达重复 | 12 | 10M | 120M |
| 完成验证器循环 | 292 | 1M | 292M |
| 合计 | ~640M |
根因分析
ZCode 完成验证器存在设计缺陷：
- 无法识别不可恢复的阻塞: 当目标因物理设备操作而无法远程完成时，完成验证器仍持续要求"继续工作"，导致无限循环
- 缺乏重复检测: 连续 60+ 次相同的失败结果未触发自动暂停
- 缺乏用户交互断点: 遇到需要用户物理操作时，应暂停并等待用户回复
建议改进
- 完成验证器在连续 N 次（建议 3 次）相同失败结果后自动暂停并通知用户
- 当助手明确报告"无法远程完成"时，完成验证器应接受该状态并暂停
- 增加"等待用户操作"状态，在该状态下不消耗 token
实际完成的工作
尽管大量浪费，本次会话完成了 28/29 个开发任务：
- 346 个后端单元测试通过
- 114 次真实 API 消融跑分完成
- iPad 真机 UI 测试通过（7 个测试）
请求
申请补偿因 ZCode 完成验证器设计缺陷导致的 ~640M token 浪费。
- Dominant language
- Python
- Stars
- 103
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from zai-org/zcode-plugins
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
zai-org/zcode-plugins#107 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
zai-org/zcode-plugins#106 ·
Maintainers usually reply within 1 day
-
video-agent-kit (0.4.3): hooks invoke python3, which doesn't exist on Windows — SessionStart/UserPromptSubmit/Stop hooks fail on every triggerPossibly taken @dvd233 claimed this 24 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
zai-org/zcode-plugins#14 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
zai-org/zcode-plugins#105 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
zai-org/zcode-plugins#88 · 1 comment ·
Maintainers usually reply within 1 day
All issues in zai-org/zcode-plugins
Similar issues
-
bug needs-triage priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
yeongseon/azure-functions-logging-python#583 ·
Maintainers usually reply within 1 day
-
documentation needs-triage priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
yeongseon/azure-functions-validation-python#546 ·
Maintainers usually reply within 1 day
-
PHP workflow streaming requests buffer the full SSE responsePossibly taken @Winoren claimed this today. Openreview: medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
langgenius/dify#44270 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
P4: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jeffknupp/association#523 ·
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
DarkStarSystems/pcons#229 ·
Maintainers usually reply within 1 day