CLI: ingest

Usage

vally ingest <directory> [options]

Description

Import eval results from an output directory into a SQLite database. This is useful for building up a historical database from multiple eval runs without starting a server.

The database can later be served with vally serve --store <path>.

Arguments

Argument	Description
<directory>	Path to eval output directory

Options

Flag	Type	Default	Description
--store <path>	string	eval-history.db	SQLite database file path

Exit codes

Code	Meaning
0	Import completed
1	Error occurred

Behavior

• Scans the directory for timestamped subdirectories containing results.jsonl files
• Each run is ingested once — re-running ingest on the same directory skips already-imported runs
• Stores outcomes, grader results, tool call events, and raw JSONL for drill-down
• Reports per-run outcome counts and totals

Examples

# Import results into the default database
vally ingest ./vally-results/

# Import into a specific database file
vally ingest ./vally-results/ --store my-evals.db

# Then serve from the database
vally serve ./vally-results/ --store my-evals.db

SQLite troubleshooting

No additional SQLite installation or configuration is required. On Node 22, a SQLite ExperimentalWarning is informational and requires no action. If an optional better-sqlite3 installation fails to load, the command reports the error rather than switching backends. See SQLite troubleshooting for repair or removal guidance shared by both commands.