The session you cannot take with you(earendil.com)
425 points by apitman 9 hours ago | 106 comments
tl;dr: Inference APIs are increasingly returning provider-sealed state—encrypted reasoning tokens, opaque compaction blobs, hidden web search context, and encrypted subagent messages—that locks sessions to a single provider and prevents users from exporting a self-contained transcript to another model. The author argues providers should make local logs canonical, keep hosted tools observable, ensure compaction and agent communication are readable/auditable, and treat distillation as legitimate rather than an "attack," so users retain the freedom to migrate sessions across models.
HN Discussion:
  • Strong agreement that lock-in is a serious, under-recognized problem worth resisting
  • Building or working on tools that keep session data user-owned and portable
  • Confirms the coupling problem with hosted tools like search/code execution creating moats
  • Not a big deal in practice since manual notes/summaries work fine for continuity
  • Concern is moot due to limited context windows and non-portable future learning