AI编码
dev.to ·
@Toruk Makto
我分析了 3 周内发给编码 Agent 的消息：40% 的输入不是真正的工作
作者并行使用 Claude Code、Kimi，偶尔用 Cursor 和 Copilot，导出 3 周内发送的全部消息并逐条标注用途（未用关键词搜索，因结果不准）。剔除自动流量后，属于本人的消息为 2,116 条，约每天 96 条。分类结果为：55% 真实工作（新任务、提问、决策），13% 纠正 Agent（做错、跑偏、未经询问更换模型或范围），9.5% 询问进度，6% 在 Agent 或会话间手工搬运信息，4% 是“go/yes/continue”等因 Agent 停下等待而发的确认，4% 要求用简单英语解释，3% 重复已给过的规则，5% 其他。作者据此认为 40% 的输入属于开销，并提到曾 200 次询问进度，其中过半集中在同一小时内的等待长任务时段。
AI推荐理由 基于个人 3 周、2,116 条真实消息的标注统计，量化编码 Agent 使用中的交互开销（40% 非实际工作），对 Agent 产品体验与工作流优化有具体参考；但为单人样本，方法细节有限，结论不宜外推。
72
正文
I run several coding agents in parallel, mostly Claude Code and Kimi, sometimes Cursor and Copilot. I felt slow, so I exported every message I sent them over 3 weeks and had each one read and labeled by what it was for. I did not use keyword search. I tried that first and it gave wrong numbers.
After removing automated traffic, 2,116 messages were really mine, about 96 a day.
What my messages were for:
55% real work: new tasks, questions, decisions 13% correcting the agent: wrong thing, drifted, changed the model or scope without asking 9.5% "what's the progress?" 6% carrying info by hand from one agent or chat to another 4% "go", "yes", "continue" because the agent stopped to wait 4% "explain that in simple English" 3% repeating a rule I had already given 5% other: slash commands, fragments
So 40% of my typing is overhead. Some details:
I asked for progress 200 times. More than half came in bursts within the same hour, while I sat waiting on long runs that finish silently.
The biggest single cause of corrections was UI work, fixed one screenshot at a time.
The same rules came back on different days and with different agents: "don't waste tokens", "ask before changing the model", "don't release until it's verified". A rule I give one agent never reaches the others.
On my worst day I relayed 33 times. Two agents were on the same experiment and I was pasting each one's report to the other.
Token anxiety is constant. Agents start big runs without saying what they will cost.
One surprise: more than half of the "user messages" in my logs were not me at all. They were scripts and test harnesses running under my normal config.
My questions:
Do you see the same problems, or is your overhead somewhere else?
Which one costs you the most?
Has anyone actually fixed the progress polling or the rules-don't-carry-over problem, especially across different tools?