Usage
user → assistant messages) in JSONL format.
Quick Start
Create a filter config (filter.toml):
Configuration
Basic Options
Score Filtering
Judge Score Filtering
Metadata Filtering
Timestamp Filtering
Complete Example
Output Format
The exported JSONL contains one example per line:CLI Options
Examples
High-Quality Dataset
Failed Examples (for analysis)
Specific Model Performance
Recent High-Scoring Traces
Workflow
Typical data collection → training pipeline:Troubleshooting
”No traces found in database”
- Verify
dbpath is correct - Check that traces were actually stored (eval/smoke with —trace-db)
- Ensure database file exists and is readable
”No sessions matched the provided filters”
- Relax score thresholds (
min_official_score) - Check metadata filters match your data
- Remove timestamp constraints
- Verify judge names match those used during eval
”TOML parser not available”
- Use Python 3.11+ (has built-in
tomllib) - Or install:
pip install tomli
Empty messages in output
- Check that traces include message data
- Verify tracing was enabled during rollouts
- Some task apps may only have prompt/completion (still exported)
Tips
- Start permissive: Begin with no filters, then tighten based on data quality
- Inspect first: Export a small
limit(e.g., 100) and review before generating large datasets - Multiple filters: Create several configs for different dataset slices (easy/hard, success/failure)
- Combine datasets: Merge JSONL files with
cat filtered_*.jsonl > combined.jsonl