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.
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
- 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.
- 02Run the same headless prompt at least twice and compare token use before trusting either number.
- 03Cut a job's cadence when its cost still won't come down: daily to 3 days a week, or alternate days.
- 04Run watchers with a mechanical trigger as plain processes. Start a model only when the trigger fires.