Agent

Agent lists every piece of work the agent does across the workspace, and opens each one as a conversation.

​

The list

Search matches the kind, the repository and the git ref. Filter by Kind, Status and Repository. Every filter rides the page address, so a narrowed list can be shared as a link, and other pages link straight into it for one repository. Work waiting its turn in the queue is a row too, because the heavy jobs run one at a time per workspace.

​

The kinds of work

The engine names two more kinds, Interface authoring and Failure adjudication. Nothing in the web app starts either one today, so neither appears in the list. Interface authoring is not missing from the product: it runs inside Flow setup, as the step that maps the program’s interfaces, and its work appears in that run’s conversation.

​

One conversation

Opening a row opens the run. The header carries the kind, the repository, the status, the short git ref and how long the work has been going. When a repository’s work ended badly, the header also offers Run again. For Flow generation it offers Resume, which continues the run rather than starting a new one. Under the header the conversation has two columns:

• On the left, the work itself: the run’s steps as headings, and under each one a row per piece of work with its status dot, its title and how long it took. The dot pulses while that work runs, and turns green, red or amber as it finishes, fails or waits. The list only ever gains rows.
• On the right, the transcript of the piece of work you picked, whole and verbatim, following its end while it runs. Which one is open rides the address.

Nothing on this page is written by the page. A row’s title is the work item the run recorded, and every message is the event as it was recorded.

​

Findings inside a conversation

A conversation can carry a finding: a disagreement the work ran into, with the same verdict buttons the Conflicts page has. You can settle it there and then, and the verdict is the same one the corpus stores.

​

Following the work

The list and the conversation both follow the workspace’s job stream, so they move on their own while work runs. A restart marks whatever was running as Interrupted; start it again from the conversation or from the repository’s Pipeline tab.

​

Next steps