At 8:38 one morning a session appeared on the board I use to see what needs me, and I had no memory of opening it.

A session is one working conversation with Claude, the AI I run my work through. The board is effectively my to-do list, so an unfamiliar session means an unfinished decision or a failure I have not seen. I went looking for the work behind it. There was none.

The record looked exactly like my work

When I finish a session, a small helper reads the end of it and writes a summary so the result can be found later. That helper is itself a Claude session, so it gets its own record in the same place as my real ones.

The record ran from 8:38 to 8:38. It had two messages, a very short reply, and a first line that read “You are reviewing the tail of a Claude Code session to produce a structured close summary.” Its card carried the project, the branch, the first line and a timestamp, same as any real session. Nothing on it said an agent had made it.

The real sessions that day looked nothing like it. One had 172 messages and another 180. By the end of the day, 5 of the 18 sessions in my log were helper summaries of one or two messages each.

The mistake was mine

The helper was never the problem. It did exactly what I asked and wrote the summary. The problem was two things I had built. I started the helper without giving it a label, and I built the board to treat every record it found as work I had started. So each time I closed a session, my own automation added something to my plate.

Guessing from the record’s shape would not have fixed it. A board that decides “short and starts with a summary instruction, so probably a helper” gets fooled the day a real two-message emergency fix arrives, or the helper’s wording changes.

What the fix was

The fix was to make every helper say what it is when it is created: what kind of work, and which of my sessions it belongs to. The board now has a section for work I started and a separate “Agent helpers, not on your plate” section for the rest, and each helper shows beside the session it summarised. Nothing is deleted or hidden. It shipped the same day and I checked it live, from the label being written through to the new section showing on the board.

Where AI fits

Claude wrote the summaries correctly. It is the board that got it wrong, by treating an agent’s housekeeping as my unfinished business. An assistant that creates records on your behalf needs to say so on each one, or you end up doing its bookkeeping.

The human decision

What counts as “mine” is a definition a person sets. A board can count records, but it cannot know whether a short session is routine or an emergency unless the record says who started it.

The lesson

Record who started the work at the moment it starts. That morning’s record was one of 5 helper sessions in a day of 18. Each one now sits under the session it summarised instead of on my plate.

The Build Log companion covers how the helper session gets created and the fields that label it.