Field notes
November 21, 2026
Write Down the No
SI agents are good at suggesting things. They're bad at remembering that you already said no. A short, plain list of what you've turned down saves you from deciding the same thing twice.
If you work with an SI agent for more than a few weeks, you'll notice something.
It keeps suggesting the same good idea. The one you already turned down. It's polite about it. It might even word it a little differently each time. But it's the same idea, and you have to say no again.
That isn't the agent being stubborn. It just doesn't know. Most agents start each session without the last one. Your yes might have left a trace, because it turned into work you can see. Your no left nothing.
The fix is simple. Write the no down.
Why the yes gets remembered and the no doesn't
When you say yes to something, it usually turns into a file, a change, or a task. The next person or agent who comes along can see it.
When you say no, nothing happens. That's the point of a no. But it means there is no evidence the question was ever asked. To anyone reading your files later, a declined idea looks exactly like an idea nobody has thought of yet.
So it gets thought of again.
What a no-list looks like
It doesn't need to be fancy. One file. One line per decision. Here are three made-up entries, written for this post, to show the shape.
- Weekly giveaway post. Said no. Too much work for the kind of reader it brings in. Only revisit if I bring it up.
- Moving the newsletter to a new service. Said no for now. The current one works. Ask again only if it starts costing money.
- Longer titles on the blog. Said no. I like them short. Don't ask again.
Each line has three parts: what it was, what I said, and when it's fair to raise it again.
The last part matters most
The first two parts stop the repeat. The third part keeps the list from becoming a wall.
Some nos are final. Some are "not now." Some depend on a number changing. If you only write "no," an agent can't tell the difference, and you'll either get re-asked too often or never asked again when things change.
"Only if I bring it up" is a perfectly good condition. So is "ask again in three months," or "ask if sales double." The point is that you decide the condition once, instead of deciding the whole question again every time it comes back.
Where to keep it
Keep it wherever your agent already reads before it starts work. If it reads a notes file first, put the no-list in that file or link to it from there. A list it never opens doesn't help.
Then add one line to your instructions: before you suggest something, check the no-list. If it's there, don't suggest it unless the condition has been met.
This is a sibling to the handoff note
I wrote before about leaving a short handoff note when an agent's session ends: what's done, what isn't, what was decided, what's only assumed: https://johndclay.com/blog/agent-handoff-note
The handoff note is for the next session. The no-list is for every session after that. One is a note on the door. The other is a sign that stays up.
The small payoff
A no-list won't make an agent smarter. It just stops you from paying for the same decision twice.
And it does something quieter, too. When you read back through it, you can see what you care about. The things you keep turning down tell you as much about your work as the things you keep saying yes to.
If you want longer pieces on how SI is changing ordinary work, they're collected here: https://johndclay.com/articles