What Flight is for
The Workflow board shows you work that needs a decision. Flight answers a different question: "What have the agents been doing?" It lists every run — in flight and finished, from Scan, from schedules, and from conversations in Chat — in one place. When someone asks "did that analysis ever run?" or "what happened to Tuesday's report?", Flight is where you look.
Open Flight in the left rail of the Workflow product.
Reading the page
Flight is a two-panel view:
Left: the run list. Every run, newest first, with the client, the agent, the status, and where the run came from. Filter it down by client using the client picker, or by the filters above the list.
Right: the run detail. Click any run to see its full story.
What a run's detail shows
What happened — the run's timeline, step by step, as the agent worked. For a run still in progress, this updates live.
Signal context — the signal that triggered the run, when there is one, so you can see what the agent was responding to.
Status — the facts: current state, when it started, when it finished, who approved it.
Why it failed — if the run failed, this section says what went wrong in plain terms. It only appears on failed runs.
Agent notes — anything the agent flagged along the way, including things to verify before shipping.
Output — the deliverable the run produced, when there is one.
Runs that came from Chat
Conversations count too. When an agent does work inside a chat, that run shows up in Flight labeled as coming from Chat. These runs don't have an approve/reject lifecycle — the conversation itself is the record — so the detail links you straight back into the chat where the work happened. Runs dispatched from a chat (for example, tagging an agent on a signal mid-conversation) also carry the Chat origin label.
Tip: When a client asks "what did you change and when?", a run's timeline plus its output makes Flight a quick, honest audit trail.
Note: Runs that are waiting on a human decision live on the Workflow board's Review column — Flight shows them too, but the approve/reject action happens on the board.