Reference
List runs and what they cost
The list-agent-runs tool, and the REST call it is generated from.
The newest matching runs, totals over every match, and with group_by the totals per value. Filters intersect. peak_context is the largest, every other counter a sum; unpriced counts runs with no cost_usd yet. A run on several tasks counts in each task or tag group. task with status=running lists the runs holding a task.
Parameters
- project
- task
Runs that worked on this task.
- upstream_of
Runs that worked on this task or anything that
blocksit, closed work included: the cost of a milestone. - tag
Runs that worked on a task with this tag.
- model
- agent
- parent
The children of this run.
- by
Runs whose recording credential is:
me(you alone, not your teams), auser_…, or ateam_…(any member). Each row'sbyis thatuser_…,nullon old runs. Your run limit:agent,status=running,by=me. - status
- linked
false: runs that worked on no task. - lingering
true: stillrunningthough every task it worked on is closed. - since
Started at or after.
- until
Started before.
- group_by
One of: model, agent, status, project, task, tag.
- limit
Rows to return, default 20;
0for totals alone.
Responses
Generated from the spec this operation is implemented against, so the two names above cannot disagree with the surface a client sees.