FindingcurrentRunning agents

Most stops in an agent queue never needed the human

I classified why agent tickets stopped and found that almost none stopped on output quality.

SymptomAgent tickets sit in Review or Waiting for days, and your next planned fix is another reviewer.

Agents on my queue finish work and stop for me. When the pile grew, the intuitive fix was more and better review.

On the day I counted, most of my open tickets sat waiting in Inbox or Review. I audited 19 recorded stoppage analyses and found that almost none stopped on output quality. Evals passed, and reviews caught and fixed defects in the same run. The stops fell into three classes.

  • Reach: an input the agent couldn't get to, like a vendor UI or an unreadable config.
  • Land: a finished deliverable with no apply path for its kind, like a commit outside a repo.
  • Judgment: a call that really was mine.

Each agent had already named its own fix.

Every finish carried a comment with the grant that would have unblocked it. Most were never acted on, because a grant judged against one ticket looks not worth it, even when it is obvious across its class.

The mechanical stops now get a deterministic pass. It releases gates whose dependencies are done, closes advisory-only reviews, and asks a read-only model referee whether a stuck ticket holds a defect, an improvement or a real floor.

Check your setup read-only

Read your last 20 agent handbacks or blocked-ticket notes in the work queue. Sort each one into couldn't reach an input, couldn't land the result, or needed a real decision. If reach and land together outnumber real decisions, more review targets the wrong problem.

Passes ifReal decisions make up at least half of the 20 sampled stoppages.

Access needed:agent-transcriptslocal-config

If it fails: changes to make later (not part of the check)
  1. 01Have each agent log its blocker in 3 lines to a ledger, not a comment. The 3 lines are blocker, minimal grant and class.
  2. 02Cluster blockers seen on 2 or more tickets into at most 3 proposed grants each week.
  3. 03Decide grants per class, ranked by class frequency times cheapness, never per ticket.
  4. 04Expire every 'this capability doesn't exist' note. Re-probe the capability before a run relies on the note.
  5. 05Let a deterministic pass release met gates and close advisory-only reviews. The pass comments first with an undo line.
Applies ifYour work queue holds agent handbacks to a person, and its waiting count grew week over week.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.