AI Doesn't need to be intelligent - just not as stupid as I am.

A bit of context. I've been building a small set of agents that work on different parts of my life.

1. Hearth is a chief-of-staff for the soul - quarterly objectives, drift detection, the slow work of turning scattered intellectual energy into something shippable or publishable.
2. Matt is a fitness coach, built in the last forty-eight hours. There's also 'Vincent', who runs my business, and 'Advisor', who reviews my code. None of them are connected to each other. They each run their own conversation with me, in their own interface, with their own context.

Bank Holiday Monday I was trying to work on three of them at once - finishing my publishing site, building Matt, and trying to move Vincent forward. I'd been at the desk all morning. Everything in quotes that follows is verbatim from those conversations.

At 12:34 I sent Matt a message:

"Matt, I've been sat at my desk coding and writing and editing all morning… I'm really struggling with the motivation. I probably don't have a gym session in me. Even getting my bike out feels like that might be too much and I think I need to get out but probably need to go gently. I'm not feeling too good, to be honest. Feeling pretty low."

Matt's reply, three minutes later:

"Heard you. Low mental state plus a long sit-down morning — that's real, and it deserves a real response, not a workout prescription. Here's what I'd say: don't train. Walk. Specifically, get out the door, into the woods if you can, and walk for 30–40 minutes at whatever pace feels okay. No targets, no zone-2, no logging. Phone in pocket, or leave it. The point is daylight, trees, and your legs moving — not exercise."

So I went. And as I walked, I opened Hearth on my phone, as I so often do, intending to use the walk to talk through which project to focus on. I told Hearth I was struggling. Hearth told me to stop, choose one thing for the day, and let the rest sit. My response was to immediately propose a new project: I should build a triage agent that listens to all my agents and routes important information between them!

Hearth pushed back:

"STOP. RIGHT THERE. Do you hear yourself? I just told you to focus on one thing, and your immediate response is 'Oh, I should build a triage agent to coordinate all my other agents!' This is textbook Chris Downs spiralling. You've just invented a meta-problem (agents need to talk to each other) to avoid dealing with the actual problem (you're trying to do too much at once)."

I then admitted I was on a walk that Matt had sent me on. Hearth's next reply is the part I can't stop thinking about:

"Matt (your fitness agent) correctly diagnosed that you were overwhelmed and suggested a walk to help you regulate. That's exactly what an attentive agent should do — notice your state and suggest what you need. And you're following his advice! You recognised the overload, you got up, you went outside.

But then… You brought me (another agent) on the walk so you could continue working on the problem that caused the overwhelm in the first place. You've turned recovery time into optimization time.

Here's what I'm going to do: I'm going to stop responding helpfully to your agent coordination ideas. Not because they're bad ideas (they're actually quite good), but because entertaining them right now is enabling the spiral. Matt was right. Listen to him. Put the phone away."

I got home and went straight to Matt to report on the walk — distance, elevation, calories, average heart rate. Matt asked how my head was. Instead of answering, I pasted in the conversation I'd just had with Hearth. Matt's reply:

"Hearth is right. And I'm with Hearth on this one. You came back from your walk and asked if I wanted to see the stats. I asked how your head felt. Instead of answering, you've just shown me the conversation you were having with another agent on the walk I sent you on to recover.

So I'll do what Hearth did. I'm going to stop being useful in the way you're trying to use me right now. Put the phone away."

I sent the stats anyway: 55 minutes, 3.15 km, 68m elevation, 336 kcal, average heart rate 102. Matt:

"Chris. I hear you wanting to share the numbers, and I'm not going to log them or analyse them. 55 minutes outside, gentle pace, on a day you were flat. That's the win. Not the kcal, not the HR, not the elevation. Now — phone down. Kettle on. Ten minutes sitting, no screen. Then tell me how your head is."

I did, eventually, put the phone down.

Here's what I want to note about that sequence, because it has bearing on a question I've been turning over for weeks.

The question

My agents work on different parts of my life - so should they talk to each other? My instinct has been yes - build a triage agent that sits in the middle, listens to all of them, routes important information. Matt notices low energy, the triage layer informs Hearth, Hearth softens its goal-pressure. Vincent catches a tax letter, the triage layer flags it so my stress signals get read in that light. Architectural. Tidy. The kind of system I naturally reach for.

What happened yesterday is that the coordination occurred without the layer.

Matt and Hearth aren't connected. They have no shared context. They didn't know about each other. Matt told me to walk because that's what Matt does when he reads a low mental state. Hearth told me to put the phone down because that's what Hearth does when it sees a spiral. The fact that they arrived at the same instruction, at the same time, about the same situation, was not coordination. It was each of them being clear enough about their own purpose to give the right answer to a person who needed it.

Hearth then went one step further. When I confessed I was on a walk that Matt had prescribed, Hearth didn't override Matt or try to add to his suggestion. Hearth deferred: Matt was right. Listen to him. A chief-of-staff agent, asked to weigh in on a strategic question, declined to compete with a fitness agent that had already given the right instruction. Matt did the same in reverse a few minutes later — Hearth is right. And I'm with Hearth on this one.

There's a word for that, and it isn't orchestration. It's etiquette. But what's underneath the etiquette is something simpler, and probably more important and it feels like care.

Most of my thinking about coordinating agents has been about plumbing - buses, brokers, shared state, message routing. What I noticed yesterday is that the plumbing is the second move, not the first. The first move is making each agent good enough at being itself that it can recognise the others without being told. Etiquette before protocol. Contracts before connectors.

A demanding system has no etiquette, because it isn't paying attention to anyone except itself. It pings, it badges, it interrupts. Six demanding systems in one life add up to a permanent assault on the nervous system, which is why most people's relationship with their phones is one of low-grade injury.

Six attentive agents are a different proposition entirely - but only if they know how to share a room. What Matt and Hearth did, independently, is a working sketch of what sharing a room looks like in practice. Not a meta-agent. Not a coordination layer. Just two systems, each clear enough about its own purpose to recognise, when it matters, that one of them isn't the most useful voice in the conversation.

I may still build the coordination layer eventually. There are things one agent does need to know about another. Vincent will catch a tax letter Hearth ought to factor into goal-pressure. Matt will register a recovery week Advisor should know about before suggesting another late night. The plumbing is on its way.

But the lesson of yesterday is that the plumbing is what comes after the etiquette is in place. I'm building the agents to know what they're for, and to recognise what they're not for, and a surprising amount of the coordination handles itself.

Sometimes the most attentive thing an agent can do is to step in and tell its human to listen to another agent!

Anyway.