Exporting session recordings

Exporting bundles a recording's storage blocks plus its ClickHouse metadata (events.json, session-replay-events.json) into a zip in object storage, for offline analysis or support. It is staff-only and writes nothing back to the recording.

There is no export API or MCP tool — a recording export is a cross-tenant, token/agent-reachable PII export, which is too dangerous to expose on the programmatic surface. Exporting (and downloading) is done only through the django admin portal, under interactive staff auth. Your job is to hand the user the right admin links.

The one rule that matters: export from the team that owns the recording