I like the idea, but this does raise a larger question about sensitive information (that you've alluded to, but I think it's more of a systemic/cultural problem). Everyone knows you shouldn't be pasting env secrets and customer data into Claude, but many do it anyway because the perceived productivity gains offered by tools like Claude Code are just too high to ignore (and the payoff is instant and the potential risk is later).

What this does though is make that visible. If someone partakes in that bad practice, then the secrets are already sitting in the transcripts on their laptop - this just moves them somewhere shared and permanent. Maybe that's enough to discourage the practice, idk. Still, not strictly your problem, but an interesting one nonetheless.

The portability angle is compelling. The interesting design problem to me is whether a resumable session artifact has to be identical to the raw transcript.

I'd love a middle layer that preserves enough state to resume and debug while aggressively quarantining obvious secret classes and high-risk blobs. Right now the tradeoff is basically perfect replayability versus shareability, and it feels like there should be a useful middle ground there.