Skip to main content
A finding is one thing Bento noticed in a trajectory: a tool call failed, the agent looped, the response drifted off the goal. It’s the smallest unit of analysis. One trajectory can carry many, and Bento groups matching findings across runs into the issues, clusters, and signals you triage everywhere else. Every finding has a kind, a short fixed label you filter on. There are 16 in total; a few of the real values: The same values feed the --kind flag on an issue’s findings and the --finding-kind filter on the Runs list.

​
Commands

A finding only exists in context, so there’s no findings command group. You pull findings from an issue or from a trajectory, and you filter the Runs list by finding kind.

​
Pull findings from an issue

This is the common path: an issue bundles its findings as evidence. Read them all, newest analysis first:
Narrow to one kind. --kind takes a single value and does not repeat:

​
Pull findings from a trajectory

When you’re on one analyzed run, list everything Bento extracted from it. This path returns all of a trajectory’s findings with no kind filter; only the issue path takes --kind.

​
Find runs by finding kind

To go the other way, start from a kind and find the runs that exhibit it by filtering the Runs list. --finding-kind repeats to match any of several, with OR semantics:

​
See also

Issues

Where findings roll up: the tracked problems you triage.

Trajectories

The analyzed runs findings are extracted from.

Signals

The detectors learned from matching findings.