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

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

By Ki Moon · 2026-10-28 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/default-to-run/

**Symptom:** Items 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 if:** A 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. File reversible local work such as code, docs, analysis and proposals as ready to run. Let the human veto.
2. Gate sends, CRM writes, spend and live config by class, not by how the item is filed.
3. Make any item marked as a decision name the call: which option, which scope, or whether it should exist.
4. Ask only when a wrong guess means redoing work. Batch questions at the end, with at most 2 rounds per thread.
5. Revisit if more than about a quarter of auto-run follow-ups are rejected over 2 weeks.

**Applies if:** Your 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.

**Skip if:** No work queue exists in your setup, or its waiting items are mostly finished work for review, not requests to start work.

Tags: autonomy, approval, agents
