export-opencode-sessions

Export OpenCode session histories to Markdown transcripts by specifying a project directory, time window, and output directory. The tool matches sessions by path and time range, writing one folder per session containing readable transcript files.

You can back up OpenCode sessions using ISO timestamps or epoch milliseconds. The exporter normalizes time inputs automatically, matching sessions within the specified window and generating individual archive files for easy review.

Auditing OpenCode session data is best handled by exporting matching sessions to individual files. The tool generates an index.json summarizing the export, providing quick traceability and audit-ready artifacts for stakeholder review.

The OpenCode session exporter supports multiple directory layouts including per-session, tree, and flat structures. You can choose the layout that best fits your archiving or review workflow when generating the export.

You can export OpenCode sessions as raw JSON files instead of Markdown transcripts. The exporter offers flexible output formats, allowing you to select either raw JSON or readable Markdown for each session artifact.

OpenCode session exports require a project directory and time window to accurately filter matching sessions from the database. This ensures only relevant session histories within the specified path and timeframe are extracted for archiving.