FindingcurrentRunning agents

Asking a headless agent to read less didn't hold

Changing the schedule held my token limit when instructions in the prompt did not.

SymptomA scheduled agent's prompt says to stop at a watermark, and its transcript shows it paging past it.

A nightly enrichment job of mine read a lot of email and meeting data, and its usage was crowding other jobs out of the shared token budget. I tried to make it read less.

I started with prose. The prompt said to stop at the watermark and not to open full threads.

The headless run ignored both.

It paged blindly through hundreds of emails and meetings, opened 19 full records, and timed out after more than a hundred turns, with no output.

Next I tried a short tool allowlist that left the agent a listing call and little else. An allowlist names the tools that run without a prompt rather than locking everything else out. The allowlist held once, then swung:

  • First run: about a tenth of the original's tokens.
  • Same prompt, allowlist and window again: eight times the first run.
  • Both covered fewer people than the original version.

A job that writes to the CRM can't ship on an 8x swing.

Changing the cadence held. One heavy job went from daily to Monday, Wednesday and Friday, the other to alternate days.

Idle time follows the same split. A watcher with a mechanical trigger runs as a plain process at zero inference and summons a disposable model only when the trigger fires.

Check your setup read-only

Take the run with the most tokens among the last 10 runs of each scheduled agent job. Read its transcript beside its prompt file. Count the tool calls the prompt told the run not to make. One or more means the prompt isn't holding the limit.

Passes ifNo sampled run's transcript shows a tool call that its prompt excluded.

Access needed:agent-transcriptslocal-config

If it fails: changes to make later (not part of the check)
  1. 01Enforce read limits in code: a turn cap, a call cap, or inputs pulled before the model starts. An allowlist shapes which tools run, not how much they read.
  2. 02Run the same headless prompt at least twice and compare token use before trusting either number.
  3. 03Cut a job's cadence when its cost still won't come down: daily to 3 days a week, or alternate days.
  4. 04Run watchers with a mechanical trigger as plain processes. Start a model only when the trigger fires.
Applies ifA scheduled headless agent's prompt file tells it to stop reading at a limit, such as a watermark or a page count.

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