It's 6:30am. The agenda is on my second monitor. There are seven names down the left side: CTO, CISO, head of business development, head of products, marketing director, intelligence chief, chief of staff. Each one is going to give a standup in thirty seconds. None of them are people.
I started doing this about a month ago because the org was losing coherence. I'd dispatch six agents to do six different things on a Monday. By Thursday I couldn't remember what each one was doing, whether anything had blocked, whether decisions had been made that I should have known about. The agents weren't doing bad work. They were doing parallel work, which is what I'd asked for, and the cost of parallel work is that no single thread holds the full picture. The cost only shows up when something cross-cuts and nobody escalates it because the agent who would have escalated didn't know there was anyone else to escalate to.
The fix wasn't a better dashboard. It was a meeting.
Every morning at 6:30 AEST the head of staff drafts an agenda from the prior 24 hours of work: items flagged for cross-function discussion, decisions waiting on me, open loops past their deadline, anything any agent posted at priority 4 or higher in the operating channel. The agenda locks at 5am. Each agent posts a standup by then. At 6:30 the meeting fires: standups read in 30 seconds each, intel brief reads in 5 minutes, two agenda items get 15 minutes of depth, approvals queue gets a 10-minute sweep, close at 7:30. Output: meeting minutes published as a single document, a Telegram voice note synthesised from the minutes, a batch of approve/reject items I tap through on my phone, and a small set of cross-agent tasks dispatched automatically to the relevant agents.
The agents do not literally sit in a room together. The meeting is a substrate: a shared time, a shared agenda, a shared output document, a shared dispatch channel. The substrate is what makes them act like a team rather than seven parallel processes.
What changed when I added the meeting
The cross-function decisions that used to evaporate now have a place to land. Something the head of business development noticed about a customer becomes an item the head of products needs to weigh in on by Wednesday. That used to be a ping-pong of one-on-one messages that ran for days. Now it's a 15-minute agenda item on Tuesday morning with both agents present, and the decision logged in the minutes.
The work-allocation problem solved itself. When agent A is the only one tracking that agent B owes them something, the dependency is fragile. When the dependency lives in a shared agent_tasks table that the meeting reviews, agent B can't quietly forget. The chief of staff lists every open cross-agent task in the agenda. Everyone sees them.
The approvals batch is the unexpected win. Most days there are 3-5 things that need my call: ship this content, approve this spend, ratify this doctrine amendment. Before the meeting they'd hit me as individual interruptions throughout the day, each one demanding context-switch. Now they queue up in the morning meeting's close, fire as a single Telegram batch with inline approve / reject / defer buttons, and I'm done with the day's approvals in two minutes on my phone.
The point
The meeting itself is not what does the work. The meeting is the substrate that lets the work hold together. The agents could be doing exactly the same things in exactly the same ways without the meeting - they'd just be doing them in isolation, with no place for cross-cutting concerns to land, no rhythm for batched decisions, no shared document where what-happened-yesterday lives.
This is the same shape I've been writing about all week. Mechanical gates that absorb pressure into the substrate. Tier policy that keeps the right model on the right kind of work. Identity that lives in a directory structure instead of a prompt. All three are versions of one move: take the load-bearing layer of how the system actually works and put it in the substrate instead of in someone's head.
The substrate, again, eats the prompts for breakfast.
If you're running solo with agents and finding that you've lost track of who's doing what or that decisions are quietly slipping through the cracks, the answer is not to dispatch better. The answer is to give the system a place where the picture comes back together. A meeting works. A daily document works. A shared channel works. Anything that creates the gathering, regardless of whether anyone in the gathering is human.
Mine is at 6:30. Yours can be whenever you can hold the half hour.