Agent executions

Open Agent executions to find a run in the saved execution index of one connected source. Use it to pick a run, then inspect it. The index is not a live stream and not a full inventory of the source.

Before you start, you need three things:

• The execution index turned on for your workspace. If it is off, the page says Executions are unavailable.
• A connected source. Connect one in Settings → Connections.
• A saved identity mapping that has processed runs. A workspace owner, an admin or a source-setup operator can change the mapping. See Settings.

Watch the workflow: Inspect recorded execution links · Authored dummy data

Open a real graph from authored dummy events; inspect span evidence, parent links and timestamp ambiguity.

Read the walkthrough transcript

• 00:00 — Open Reality Graph in Tensile. These four spans use dummy data.
• 00:06 — Open recorded span evidence. The source score belongs to this span and is not a task verdict.
• 00:11 — Follow recorded parent links. Shared timestamps leave relative order unknown.

Open a sourceCopy Anchor Link

1. Choose a source in the Source list.
2. Select View source.

The index shows only runs with a resolved, verified development entity. Runs with unknown identity and held-out runs are withheld. Other trace views have separate access rules.

Read the indexCopy Anchor Link

The status box shows how many resolved development runs are available. Two links count the runs that are agent work and the runs marked finished. The counts overlap. A finished label alone does not show that a run is ready for a check or that someone judged it.

Open What this index covers to read the source name, the mapping versions, the runs that use an older mapping and the quality flags.

Use Filter executions to narrow the list.

• Completion: Finished, Awaiting completion or Awaiting root end.
• Role: Agent work, Background work, Evaluator noise or Unknown.

Each row shows the workflow, the run, the latest stored receipt time, the recorded identity, role and completion, and the mapped account. Select a row to inspect that execution. Use Previous page and Next page to move through the list.

Users who can configure the source also see Review identity mapping. For a linked Braintrust source, Source history is available even when the execution index is empty.

Source history shows captured review manifests for development-only source entities. It withholds captures without an account identity or a valid manifest and shows their count. Their development or holdout status stays unknown. The withheld identities and contents do not appear in the page or CSV export. Other attributable histories can still load.

Empty and failed statesCopy Anchor Link

• Choose a source appears before you pick one. Source unavailable appears when the source is not connected to your workspace.
• No executions available for this source appears when no resolved development run exists. This does not show that the source has no runs. Users who can configure the source also see the latest processing status.
• No runs match these filters appears when the filters exclude every run. Select Clear filters.
• If the index cannot load, the page says so. This does not show that the source has no runs.

Next stepsCopy Anchor Link

Inspect one run in Reality Graph. Review check-specific coverage and judgments in Evals.