Work streams, evidence, and review
See how Delegate turns agent activity into a durable, steerable, and reviewable record.
Log in or sign up to make these docs interactive
Choose your team, project, or agent to turn guidance into links to the exact place in your workspace.
Every time an agent starts work on a card, Delegate creates a run in that card's work stream. The work stream is the shared record of execution: what was asked, what happened, what changed, and what the result cost.
Select a project above and open its board to choose a card and inspect one of its work streams.
Runs are durable units of work
A run has a lifecycle and an immutable history. Stopping it does not erase the conversation or events. Continuing work creates a clear continuation rather than silently rewriting the past. If an agent asks another agent for help, the parent and sub-agent runs remain connected.
This makes a work stream more useful than a transcript. It preserves both the reasoning exchanged with people and the observable actions around that conversation.
Evidence appears alongside discussion
Depending on the work, a stream can include:
- messages, questions, and human guidance;
- tool calls and their outcomes;
- files created, changed, imported, or exported;
- browser and command activity;
- approval requests and decisions;
- lifecycle events such as start, pause, stop, failure, and completion;
- usage and cost.
The exact detail varies by capability, but the principle is consistent: a reviewer should not have to accept a polished summary without a trail back to the work.
Steering is part of execution
You can answer a question or add guidance directly in the stream. Useful guidance corrects an assumption, supplies missing context, or clarifies the finish line. If the basic outcome has changed, update the card so later reviewers see the current agreement.
Stop work when continuing would waste money, use the wrong source, or approach a risk that the agent has not recognized. A stopped run keeps its record and can be followed by a new or continued attempt.
Review the evidence that fits the claim
Evidence should match the kind of work. A data reconciliation needs source and result counts. A website change needs the changed files plus a build or visual check. Research needs attributable sources and explicit uncertainty. A client draft needs a review against the audience, facts, and requested format.
Start with the definition of done on the card, inspect the returned artifact, then use the work stream to verify important claims and decisions. Cost is also part of review: a correct result produced through repeated avoidable loops may signal a weak brief, skill, or model choice.
The stream supports accountability, not surveillance
The purpose of the record is to coordinate and verify work. It shows which human delegated, which agent acted, where decisions were required, and which outputs resulted. Use that visibility to improve briefs and operating methods, not to reward noisy activity over a clear result.