Engine History
Engine History is the agent ledger for a project. Every engine run is logged with who ran it, what inputs it had, what came back, which model and version produced it, the cost and the duration, and is kept until the project is deleted. Every AI output has a replayable receipt, which makes Trueleveler audit-defensible.
What does Engine History show?
Engine History is the agent ledger: every engine run in a project is logged — who ran it, what inputs, what came back, what model, what version, cost, duration — and kept until the project is deleted.
This is what makes Trueleveler audit-defensible. Every AI output has a receipt, and every receipt is replayable.
Per-run detail
- Run ID · stable identifier · cited from other reports and Pulse answers
- Engine + version · which engine, what prompt revision
- Operator · who triggered the run (user, automated event, schedule)
- Inputs · documents, parameters, prior-run references
- Outputs · extracted items, summary, generated artifacts
- Cost · in cents · for billing reconciliation
- Duration · wall-clock ms
- Model + prompt hash · for exact replay
Filtering and search
Filter by engine, operator, status, date range. Search by run ID. Export the filtered set to CSV or as a single combined PDF (one report per run).
Re-running a run
Click "Replay" on any run · this re-runs the engine with the original inputs. Useful when a prompt has been updated and you want to re-evaluate prior conclusions. Replayed runs link back to the original via replays_run_id.
Retention · until the project is deleted
Engine History rows are kept until the project is deleted. Underlying audio (Meetings) and document files follow their own retention rules; the engine_run row stays regardless.
Email support.
Priority support on Business and Enterprise plans. support@trueleveler.com