/history) in the web app to see runs across the projects you can access in the active organization. Get there from View runs in an agent’s menu, a pinned run, or a link to a run; each workflow also lists its own runs.
What appears in Runs
Runs includes two run types:
The table shows each run’s name, type, start time, actor, status, trigger, duration, and project. Additional columns are available for run ID, queue time, finish time, models used, other services used, billed amount, message count, step count, and raw trigger value.
You can search runs, filter by fields like status, type, project, trigger, actor, model, service, cost, messages, and steps, or use the saved views for failed and running runs.
Statuses
Runs can have these statuses:
Active runs update automatically while they are queued, running, sleeping, or waiting on a hook.
Inspect a run
Select a row in Runs to open the detail panel. The panel has three tabs:
Agent runs show the recorded conversation in the Overview tab. Workflow runs show input and output payloads, or an error payload when the run failed.
The Trace tab is the lowest-level view. Spans nest to mirror what actually ran: a trigger run wraps the workflow run, which wraps each action, agent, and model step, which in turn wrap nested tool calls. Reading the spans shows what ran, in what order, and where time and errors went.
Use the CLI
Useluno history when you want organization-level cloud history from the terminal:
luno history list uses the active cloud organization and can filter by project ID, status, and kind. Owners and admins can pass --admin to list all organization resources.
For resource-specific inspection, use the agent and workflow run commands:
Next steps
Agent runs
Inspect agent sessions, conversations, tool calls, and traces.
Workflow runs
Inspect workflow input, output, errors, steps, and traces.
Run agents
Start agent sessions and inspect their results.
Run workflows
Start workflow runs and review their output.