cd /news/ai-agents/i-analyzed-3-weeks-of-my-own-message… · home topics ai-agents article
[ARTICLE · art-135288] src=dev.to ↗ pub= topic=ai-agents verified=true sentiment=· neutral

I analyzed 3 weeks of my own messages to coding agents. 40% of what I typed was not real work. Is it the same for you?

A developer analyzed 2,116 messages sent to coding agents including Claude Code, Kimi, Cursor, and Copilot over three weeks and found that roughly 40% of typed input was overhead rather than real work. The breakdown showed 13% of messages were corrections, 9.5% were progress checks, and 6% were manual information relay between agents, with the developer noting that "a rule I give one agent never reaches the others." The developer also found that more than half of logged user messages came from scripts and test harnesses rather than the human operator.

by read2 min views1 publishedSep 20, 2026

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?

── more in #ai-agents 4 stories · sorted by recency
── more on @claude code 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/i-analyzed-3-weeks-o…] indexed:0 read:2min 2026-09-20 ·