- tags
- #help #history #wip
- description
- how long the agents' runs take
- brief
- How long the agents' runs take: one row per run with each step's minutes, and medians per step. Query only, opens on the last 7 days.
Help: Performance¶
Master projects. Performance (Log:Performance) is for analysing agent runs: every run a coder (or another agent) finishes leaves its timings — launch, reading, setup, build, tests, merge, docs, checkpoint, deploy — and where it ran (cloud, laptop, dispatched). The page is a query: it opens on the last 7 days with a summary line (runs, median minutes per step, fixed time vs time per task, each runner apart) and one row per run. Change the range, the agent or the runner to compare.
Retention and the archive¶
- Kept on the project: 7 days.
- Archived: every night, the entries from whole days (UTC) older than that (every kind: decisions, changes, AI work, pipeline, runs) are written to one file in the project's Files, folder
_archive/, namedhistory-<first day>--<last day>.jsonl.gz, then removed from the project. A day that hasn't ended (at midnight UTC) is never archived. - The file: gzipped JSON Lines, one entry per line with all its fields; opens with any gunzip. Members of the project can download it. A query reaching back further than 7 days names the files that cover it.
- If archiving fails nothing is removed; it is retried the next night (see the history archive cron on the Crons page).
- Archive files stay in the Files page's
_archive/folder until the project's archive size quota is reached; then the oldest are deleted first.