Data Export

Export all traces in a namespace as a ZIP of JSONL files, and optionally push to HuggingFace.

Export every trace in a namespace for offline analysis, fine-tuning datasets, or archival. Available on personal namespaces and organizations.

Create an export

Open Settings → Exports in your namespace.
(Optional) Set a date range or visibility filter.
Click New Export.

Exports run in the background. The page updates as status changes — no need to refresh.

Download

When the export is ready, use the Download button on the row. Files are named {namespace-slug}-export-{unixtime}.zip, where unixtime is the Unix timestamp at creation.

What's inside

The ZIP contains one JSONL file per entity type plus a manifest:

manifest.json — export metadata and record counts
traces.jsonl — one trace per line
messages.jsonl — one message per line
parts.jsonl — one part per line (tool calls, thinking blocks, etc.)

JSONL loads directly in tools like DuckDB, pandas, and BigQuery without preprocessing.

Retention

Completed exports are kept for 48 hours, then expire. The record stays in your history as expired; create a new export to get a fresh download.

Delete an export

Use the Delete button on any export row. Running exports can't be deleted until they finish or fail.

Push to HuggingFace

Completed exports can be pushed directly to a HuggingFace dataset repo.

Connect HuggingFace first from Settings → Integrations, and create the destination dataset repo on HuggingFace if you don't have one. The upload button is disabled until the integration is connected.

To upload, click Upload to HuggingFace on a completed export row, pick the destination repo, and optionally set a subdirectory path. The JSONL files are pushed as a single commit, and a View on HuggingFace link appears with the commit URL when done.

Limits

Each file in the export must be under 50 MB. If an export exceeds this, narrow it with a date range filter.