session-export

Export coding agent sessions for sharing and code review by finding the target session with cass sessions and running cass export to your preferred format. This enables quick reviews, audits, and knowledge transfer across current or workspace sessions and project histories.

Agent project histories can be archived in Markdown, plain text, JSON, HTML, and self-contained encrypted HTML formats. Multiple export options ensure compliance and reference preservation for various archiving needs.

You can generate a self-contained HTML file for coding session documentation using the cass export-html command. This produces an encrypted, standalone file ideal for securely sharing session histories with stakeholders.

Exporting agent sessions requires no external dependencies. The skill operates independently using built-in cass export and cass export-html commands to process workspace sessions and project histories directly.

The best way to transfer coding session knowledge to teammates is exporting the session to Markdown or HTML formats. This enables easy collaboration, quick reviews, and seamless documentation sharing without requiring teammates to access the original workspace.

JSON format should be used when exporting agent sessions to preserve structured data for audits and integrations. It captures the complete session history in a machine-readable format, enabling downstream processing and compliance tracking.