This week I sat down with one of my sons and worked through his math homework with him. Afterward he came back, said thanks for helping, and gave me a hug. That is the kind of moment I am building for: more time to play a game with my kids, help them with their homework, more presence.

I opened the dashboard and saw the same thing I had seen for weeks: a handful of cards, most of them waiting on me. The agents had been running every day, the logs showed completed work, and still nothing moved forward. I figured the autonomy just was not taking hold yet.

Then one of the runs surfaced a different number. Not the count of cards, but the count of runs that had finished and marked themselves "pending review." One hundred and ten. One hundred and ten pieces of work sitting in a state the surface never showed.

The status was not lying on purpose. It was just reporting what the agent believed had happened. The pipe that was supposed to turn that belief into something I could see had never been wired. So the work existed, the review never did, and I kept thinking the agents were not delivering.

That is the part that sticks. When your agents look idle, the first thing to check is not their effort. It is whether the thing they are reporting actually reaches you. A status is only as good as the surface that renders it. If the surface is missing, the status becomes a private claim the boss never sees.

I have started treating every "done" or "waiting" as a telemetry event instead of a promise. The run either emitted an artifact I can open, or it did not. The card either appeared in the queue, or it did not. Everything else is a story the agent is telling itself.

The practical move is small. Before you ask why the agents are not moving faster, pull the last ten runs and ask what actually left their hands and where it landed. If the answer is "it should have shown up here," you have found the real constraint. Fix the pipe before you rewrite the prompt.

First in the Building with Agents series: real lessons from running a company on AI employees.

What I am working on now is FreedomOS: a way for founders like me to run AI employees so the work actually surfaces, gets decided, and frees the evenings for homework and games. You are watching that build from the inside of this list.

If a night with your kids keeps getting postponed because work will not leave your hands, hit reply and tell me what is stealing it. Or forward this to one builder who needs the same reminder. More writing lives at timlinnet.com.