FindingcurrentRunning agents

Most of my agents' questions shouldn't have been questions

Seven in ten held items asked me whether they should run.

SymptomItems waiting on a human pile up in your agent queue while the dispatcher uses a fraction of its capacity.

My agents file follow-up work to a ticket board that other agents pick up. The default for anything uncertain was "decide whether to run", which turned every cheap, reversible follow-up into a go/no-go question for me.

It looked like a throughput problem, though the limit was my attention.

  • Held items asking only whether to run: about 70%.
  • The same share in August: 90%.
  • Dispatcher use: under a third of its daily capacity.

So I flipped the default to run, with a veto. Reversible local work runs on the next pass and I drag back what I don't want. Sends, CRM writes, spend and live config stay behind structural gates however a ticket is filed.

Inside a session the same logic is a redo test. A question qualifies only if a wrong guess means redoing work, or if it is an approval gate. Everything else gets a stated default.

Check your setup read-only

Read the items in your agent work queue that are waiting on a person. Count the items that only ask whether to run reversible work. More than a third means your filing default is the bottleneck.

Passes ifA third or fewer of the queue items waiting on a person ask only whether to run reversible work.

Access needed:local-config

If it fails: changes to make later (not part of the check)
  1. 01File reversible local work such as code, docs, analysis and proposals as ready to run. Let the human veto.
  2. 02Gate sends, CRM writes, spend and live config by class, not by how the item is filed.
  3. 03Make any item marked as a decision name the call: which option, which scope, or whether it should exist.
  4. 04Ask only when a wrong guess means redoing work. Batch questions at the end, with at most 2 rounds per thread.
  5. 05Revisit if more than about a quarter of auto-run follow-ups are rejected over 2 weeks.
Applies ifYour work queue is the board, ticket list or file where agents file items for a person to act on. It holds agent-filed items waiting on your go-ahead, and the dispatcher's run log shows idle slots.

← 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.