Export transcripts

Export a session's conversation history and task log for documentation, review, or analysis.

Export mid-session with /export

The /export slash command writes the current session's transcript without leaving Cantrip. It works the same way in the TUI, CLI REPL, and Web UI:

› /export
› /export markdown
› /export jsonl /tmp/session.jsonl

Syntax: /export [html|jsonl|markdown] [path]. Both arguments are optional — without them Cantrip writes transcript.html into the charm directory. The first positional argument selects the format; a trailing token becomes the output path. The command runs against the live .cantrip store, so you can grab a snapshot at any point without pausing work.

Export from the command line

Outside a session, export the full transcript as an HTML page:

$ cantrip export-transcript /path/to/my-charm

This creates transcript.html in the charm directory. Open it in a browser to see the complete conversation, tool calls, and task results.

Choose a format

Three output formats are available:

$ cantrip export-transcript /path/to/my-charm --format markdown
$ cantrip export-transcript /path/to/my-charm --format jsonl

Filter the transcript

For long sessions, filter the export to focus on what matters:

By task

$ cantrip export-transcript ./my-charm --task build_charm_code

By phase

$ cantrip export-transcript ./my-charm --phase research
# Options: research, build, deploy, test

By timestamp

$ cantrip export-transcript ./my-charm --since 2026-04-15T10:00:00Z

Paginate HTML output

For very long sessions, split the HTML output into multiple pages:

$ cantrip export-transcript ./my-charm --page-size 50

This creates transcript_1.html, transcript_2.html, etc., each containing 50 conversation messages. Navigation links connect the pages.

Custom output path

$ cantrip export-transcript ./my-charm --output /tmp/my-report.html