Part of: this research — view all 6 rows
Current State and Resolution Requirements Resolving this question requires both a published, cross-provider specification for exporting accumulated model personalization (memories, preferences, or learned weights) and implementation by at least two of the top five AI labs (Anthropic, Google, Mistral, OpenAI, xAI). As of mid-November 2026, no such standard exists. Existing interoperability tools are strictly vendor-specific import features designed for customer acquisition. For instance, Anthropic supports pasting plain text for memory imports elicitation.substack.com, while Google's Gemini accepts ZIP files of ChatGPT conversation history gemini.google. These do not satisfy the criteria for a shared standard.
The Gap Between Specification and Adoption Drafting a specification is not the bottleneck; several published candidates already exist. The Portable AI Memory (PAM) v1.0 specification details a JSON format for preferences and memories portable-ai-memory.org, and the Data Transfer Initiative (DTI) publishes an AI Conversation Schema 2 sources. Similarly, the W3C AI Agent Memory Interoperability Community Group has a mandate to build profiles w3.org. However, none of these efforts boast participation or implementation by any frontier lab. Furthermore, the widely adopted Model Context Protocol (MCP) explicitly lacks a memory primitive, and its 2026 revisions increasingly push the standard toward statelessness aaif.io.
Market Incentives Against Standardized Exports The primary hurdle is structural disincentives. While interoperability standards like MCP and Agent Skills were adopted quickly because they expand model capabilities and benefit the provider ecosystem 2 sources, a memory-export standard actively weakens user lock-in. Market leaders—Anthropic in enterprise API spend and OpenAI in consumer chat—have strong incentives to offer generous, proprietary import tools while keeping exports limited to plain text or unstructured JSON. There is also diminishing pressure for a formal data schema; DTI’s Vision 2030 report specifically advocates for relying on AI-mediated translation rather than strict, shared memory schemas 2 sources.
Regulatory and Technical Headwinds Regulatory mandates are unlikely to force adoption within the roughly two-year window. The EU's Digital Markets Act review recently declined to designate generative AI as a regulated platform category techpolicy.press, and AI-generated memory summaries may be classified as "inferred data" falling outside GDPR data portability rights medium.com. Moreover, if continual learning eventually personalizes models through live weight updates or adapters, exporting this state across entirely different proprietary architectures becomes a prohibitively difficult technical challenge, rendering text-based standards insufficient.
Paths to a Qualifying Standard Despite the long odds, I assess a 13% probability because there are a few narrow paths to implementation by late 2028. Trailing labs—such as Google or Mistral—could adopt a lightweight JSON schema like PAM to pressure market leaders on openness and data portability. Alternatively, the Agentic AI Foundation, which governs MCP and includes several top labs, could eventually pivot to include a memory extension. However, given the strong retention incentives and the complete lack of current lab engagement in memory standardization, the chances of two frontier labs voluntarily shipping a shared export standard remain low.
Set against related questions, this estimate was held stable, reflecting the view that leaders will rely on technical friction to constrain switching rather than adopt shared export standards.
Ask a followup
Sign in to run · $20 free credit, no card · every claim cited