How Run works

Building an agent is only half of it — the other half is work actually arriving and getting done. This page maps every path by which work reaches an agent in the Komodor Agentic Operation Platform (KAOP), explains what a run is and what it leaves behind, and points you at the page for each surface.

​

Eight ways work starts

Work arrives from wherever your team already is. Whatever starts it, the result is the same object: a run. Every run records the surface that started it, so an alert-driven investigation is never confused with a manual one:

​

What a run is

A run is one execution of one agent, recorded durably from the moment it is created to the moment it reaches a terminal state. It carries its own input, its own evidence, its own output, and its own cost, and it is addressable forever after. Runs move through a small set of statuses: Work is never pushed at a worker — a worker claims runs from the control plane’s queue. That is why an agent needs only outbound access to KAOP, and why a run that is waiting is honestly reported as queued rather than quietly stalling. See Architecture.

​

What a run leaves behind

Nothing about a run is reconstructed after the fact. The agent streams its evidence back to the control plane while it works, and that stream is what you read later:

• Transcript — the human-readable narration: progress notes, tool calls and their results, data the agent pulled, drafts it produced.
• Trace timeline — the structured span tree of reasoning, model calls, and tool calls, with the time each took.
• Logs — timestamped log lines, at the usual levels.
• Output — the final result, in two channels: machine-readable fields for automation, plus an optional human-readable markdown rendering.
• Artifacts — discrete files the run produced, which you can open and download.
• Usage — model, token counts by class, and cost.
• Guardrail decisions — any action a policy blocked, redacted, or held for approval.

That collection is what makes an agent’s conclusion auditable instead of something you take on trust. Runs & evidence is the page on how to read it.

​

Where the work is visible

• History lists every run and every chat session in one ledger, newest first, filterable by type, status, agent, and free-text search.
• A run’s own page holds its evidence, and the composer beneath a finished run’s output lets you ask a follow-up, re-run the agent, or hand the run to a local coding agent.
• Attention lists everything currently waiting on a person — a held action to approve, a choice to make, a workflow run that stopped and needs review.

​

Explore Run

​

Next steps