{
  "id": 3473683,
  "title": "I Treated Agent Sessions as Portable Cache and Moved Control to a Policy Plane: Vendor Lock-In Became Manageable",
  "url": "https://urgent.news/2026/08/26/i-treated-agent-sessions-as-portable-cache-and-moved-control-to-a",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-26T09:05:21.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/jangwook_kim_e31e7291ad98/i-treated-agent-sessions-as-portable-cache-and-moved-control-to-a-policy-plane-vendor-lock-in-15j4"
  },
  "original_language": "en",
  "account": "The article explores the implications of portable agent sessions in reducing vendor lock-in. The author froze a real Claude Code session, converted it into seven different formats using session-migrate 0.8.0, and observed the results. While the conversation and tool context transferred well, the controls that make the agent safe for an organization did not move at all. The operational problem lies in the portability of approval and audit, not the portability of a developer's local transcript.\n\nThe article highlights the distinction between moving the chat history location and ensuring the context of agent actions is preserved. The author explains that session files can contain sensitive production data and that converting them to another vendor's format could lead to unintended data export. Slack Code is mentioned as an alternative that moves durable work records to a shared operating surface while inheriting existing permissions and administration planes.\n\nThe author emphasizes the importance of portability at the policy plane rather than the transcript. Session migration supports 12 harness formats and describes 144 ordered routes, but authentication, hooks, policies, MCP, and runtime configuration remain bound to the source client. This architectural fact should be considered in vendor discussions. The article concludes by outlining the limitations of migration, particularly the inability to transfer authentication, hooks, policies, and runtime configuration.",
  "summary": "I wanted to know whether portable coding-agent sessions materially reduce vendor lock-in, or merely make a future migration look easier than it is. I froze one real Claude Code session, inspected it, and transferred it into seven target formats with session-migrate 0.8.0. The useful conversation and tool context traveled surprisingly well, but the controls that make agent work safe in an…",
  "key_points": [
    "Portable agent sessions reduce vendor lock-in.",
    "Controls for agent safety not portable across vendors.",
    "Policy plane portability crucial for manageable lock-in."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}