Tracing 44 agent calls: 84% were decisions, not writing
The author tagged 44 calls from a support-triage agent run as write or decide, found 37 only picked a branch, and proposed splitting work so Claude writes, Jev decides, and code executes.
holy sh*t, i traced 44 calls from one agent run and 37 of them never wrote a word illustrative trace of a support-triage run, every call tagged with one label > write: it ends up as text a person reads > decide: it only picks the next branch, then gets thrown away here's how the 44 split: > 7 writes: reply drafts, a plan, a summary > 37 decisions: which step next, is this source useful, is the draft ready, which tool, escalate or not that's 84% decisions, and it's not unusual for agent setups what actually got me is how most of us run it. we pay writing prices for decision work, a prose model spends paragraphs on a fork that already had a known answer the fix is a split > claude creates > jev picks, scores and gates > code does the thing a decision comes back as a typed answer with a probability in 70 to 500 ms (vendor figures), so your code acts on high confidence, reviews the middle and escalates the low try it tonight: log one run of your agent, tag every call write or decide, count save this for your next agent build how many of your agent's calls actually write something? full 24/7 stack in the article below ↓
This post quotes another post: x.com/kiruwaaaaaa/status/2109593981122195661