Bale Chat Exporter

Problem

Chat archives contain private messages, identities, timestamps, replies, forwards, and media. Exporting them manually is slow; automating the job without visible safeguards is risky.

Capabilities

The CLI lists available dialogs, requires an explicit selection, paginates through history with duplicate protection, normalizes provider objects, and writes a timestamped export. The result includes result.json, a short README, and optional images, videos, audio, voice, and documents folders. Bale Chat Exporter terminal workflow

How it works

Command handling, export orchestration, provider introspection, dataclass models, and filename safety are separated. Tests cover pagination, repeated pages, normalization, and media fallbacks without requiring a live Bale account.

Constraints

Session files, raw provider data, direct media URLs, and exports remain sensitive. Confirmation is explicit; filenames are sanitized; --no-raw and --no-media support safer output and smoke tests. A successful export never implies permission to publish it.

Bale Chat Exporter

Problem

Capabilities

How it works

Constraints

Related projects

Avangaar

NeTab