---
title: "Stop Paying a Thinker to Watch for Yes or No"
canonical: https://dxdev.com/blog/2026-07-19_stop-paying-a-thinker-to-watch-for-yes-or-no/
datePublished: 2026-07-19
---
A scheduled AI task ran for fifteen minutes that morning, spent most of a day's budget, and still failed to deliver a single result.

That job's whole purpose was reading a handful of sites overnight and dropping a short summary into a shared notes file every morning. It was a reasonable use of a smart assistant when it was set up. It just cost a lot to run every single day whether or not anything worth reporting had actually happened.

## The night that made the cost visible

That same evening, a different, unrelated question came up: had a business partner posted an update yet. Out of habit, that question went to the same capable-but-metered assistant. It ran for a couple of minutes and came back with a single word: an error, no explanation. A different assistant, one that wasn't metered the same way, took the same question and answered it in under thirty seconds.

The natural read of a bare error is "something's broken, try again" or "the connection hiccuped." That's a bad way to read a balance. What had actually happened was straightforward and boring: the morning's expensive run had already spent almost everything, and this second, smaller ask was the one that emptied it out entirely. An error with no number attached looks exactly the same whether the cause is a flaky connection or an empty wallet, and there's no way to tell which from the message alone.

## Naming what the job actually was

Looking at both failures side by side made the actual shape of the problem obvious. The morning job wasn't really "go think about the news." It was a poll: check if anything new and worth mentioning showed up, and most mornings the honest answer barely changes. The thing that mattered that night wasn't a summary of the internet. It was one specific fact: had the update landed yet, so the reply could go out promptly.

That's a "yes or no" question, not a "think it through" question, and it had been assigned to the expensive option purely out of habit.

## What replaced it

The daily assistant job was swapped for a small, unglamorous script: check the shared workspace every few minutes, and only say something out loud when there's actually something new to report. No model reads it, no reasoning happens, nothing is spent when nothing has changed. It runs constantly and costs nothing per check, which is the opposite shape of a job that runs once and costs a lot whether or not it finds anything.

The daily assistant job stayed off after that. If it comes back, the plan is a balance check in front of it, so a dead job shows "no credits left," not a message that looks like a shrug.

## The rule worth keeping

Not every recurring check deserves a thinker. Some questions genuinely need judgment: is this news item actually relevant, does this pattern mean something. Plenty of others are a plain comparison wearing a fancier job title: did the number change, did the file update, did the message arrive. The second kind doesn't get smarter by paying more for it. It gets a watcher that costs nothing to run and only speaks up when there's actually something to say, and the first sign you've been paying for the wrong kind is usually a bill, or an error, that doesn't tell you why.