The map told you where each piece goes. This one follows a single run, moment by moment, and shows the code that renders each one.
Two days ago we drew the map of an agent interface : seven places every agent app shares, and which component belongs in each. That answered where .
This post answers when , and how . An agent run is a sequence of moments: someone asks , the agent thinks , it acts , it stops to get an approval , it answers , and someone who cares about cost or bugs observes the run afterwards. Cuelark UI's agent kit is 29 React components for shadcn/ui, grouped by exactly those moments.
We'll follow one run through all six, with the real props for every component. The run is fictional (file names, counts and timings are made up for the example), but every API is the one in the registry.
The run: "Invoice totals are a cent off for EU customers.…