The Session You Cannot take with you
The article discusses how modern inference APIs increasingly embed provider‑bound state that limits the portability of AI session transcripts. It proposes a set of criteria—inspection, export, replay, audit, and deletion—to evaluate true session ownership and highlights the distinction between user‑controlled data and provider‑sealed encryption. The author expresses concern that current practices shift operational control away from users toward providers.
- ▪The original promise of a simple input‑output inference API is eroding as providers add opaque, encrypted blobs and server‑side references that users cannot access.
- ▪A portable session should allow a transcript to be exported and continued on a different provider without needing the original provider’s decryption keys or IDs.
- ▪The authors define five tests for session ownership: inspection, export, replay, audit, and deletion.
- ▪Provider‑sealed encryption may offer privacy benefits for zero‑retention customers but does not give users control over the encrypted content.
- ▪The shift toward provider‑controlled state changes the reality of session ownership, making the user’s transcript only a partial view of the full session.
Hacker News (Front Page) files mainly under programming. We currently carry 853 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Earendil |
| Canonical URL | https://earendil.com/posts/session-portability/ |
| Publication time | Fri, 31 Jul 2026 03:47:59 +0000 |
| Retrieval time | 2026-07-31T04:27:39.845Z |
| Last seen | 2026-07-31T04:27:39.845Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
The Session You Cannot Take With You Date:Thu, 30 Jul 2026 From:Earendil Engineering <[email protected]> To:You Subject:The Session You Cannot Take With You The original promise of an inference API was wonderfully simple: send some input, receive some output. If you kept both, you had the conversation. You could inspect it, archive it, replay it, or give it to a different model. That abstraction was never completely true. Prompt caches live on somebody else's GPUs, tokenization differs between models, and sampling is not reproducible (and quite intentionally so). But the semantic record of a session in the form of a transcript could still belong to the user. A transcript should contain the instructions, messages, tool calls and tool results.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Earendil.
Discussion
0 commentsMore from Earendil
