{{ t.f1t }}
{{ t.f1b }}
essay
2026-08-18 · 6 min · Vibisual
A log tells you what happened, in order. A map tells you where everything is, right now. Agent runs need the second one.
A terminal is a good instrument for one worker. One cursor, one column of output, time running downward. When you were the one typing, that shape matched the work exactly.
Five agents break it. Output from unrelated tasks interleaves, the thing you care about scrolls away while you read something else, and the question you actually have — which one is stuck? — gets answered only by paging back through text that has already moved.
So we stopped printing the run and started drawing it. A node per agent, an edge per handoff, a child bubble per tool call. Position carries meaning, and state is a colour instead of a sentence you have to find.
The surprising part was not the map. It was that the same canvas turned out to be the right place to design the team: if a graph is how you read a run, a graph is also how you write one. Configuration and observation ended up being the same picture, seen at two different times.
{{ t.nameLine }}
{{ t.sub }}
{{ t.canvasCaption }}
{{ t.vdeLead }}
{{ t.f1b }}
{{ t.f2b }}
{{ t.f3b }}
{{ t.instLead }}
{{ t.instSrcBody }}
Contributing →{{ t.statusBody }}
{{ t.secBody }}
{{ t.ctaSub }}
{{ ui.blogLead }}
{{ art.excerpt }}
{{ pa.v }}
{{ doc.lead }}
{{ pa.v }}
{{ s.note }}
{{ t.ideAnnoLead }}
{{ an.b }}
{{ an.k }}