The dream of seamless AI portability is colliding with the reality of proprietary silos. In a recent discussion sparked by Mark Cuban, it became clear that while exporting simple prompts is easy, moving the accumulated context, skills, and memories built up over months of usage is a logistical nightmare. The core issue isn't just about swapping chatbots; it's about the inability to transfer the 'junk drawer' of learned facts and project-specific workflows between different AI ecosystems like Claude, Codex, and Gemini without losing critical data integrity.

The Two-Layer Problem

Craig Tracey, CEO of SixDegree, argues that current AI memory is little more than a collection of random, low-value facts like 'prefers aisle seats,' making migration trivial. However, Cuban counters that this view ignores the high-value layer of project-specific skills and repeatable tasks. The truth lies in the middle: the top layer of configuration, such as AGENTS.md and SKILL.md files, is increasingly standardized. With tools like rulesync boasting a million monthly npm downloads and the Linux Foundation’s Agentic AI Foundation backing these formats, moving your agent's 'instructions' is becoming feasible. But this is where the ease ends.

Memory and History Are Still Siloed

The real bottleneck is memory and chat history. There is currently no universal standard for exporting an agent's long-term memory. Platforms like Claude Code and Cursor use proprietary transcript formats that can change without notice, and none offer APIs for reading or writing memory directly. Users are forced into a 'game of telephone,' manually pasting context between tools, which leads to data loss and corruption. Furthermore, memory is dynamic; some tools automatically prune unused entries, meaning any export is just a temporary snapshot rather than a permanent record.

The Open-Source Workarounds

Developers aren't waiting for vendors to fix this. A vibrant open-source ecosystem has emerged to bridge the gap, with projects like claude-mem (102,000 GitHub stars) and Mem0 (67,000 stars, $24M raised) providing external memory layers. Tools like SpecStory and Entire save sessions as Markdown or git refs, allowing for some degree of portability. However, this space is volatile. ByteRover archived its repo in September 2025, and Meta shut down the capture product behind Rewind after acquiring Limitless. Choosing an open-source memory layer to avoid vendor lock-in can ironically lead to a different kind of dead end if the project itself becomes unmaintained.

Regulatory Uncertainty

Regulators are circling but haven't landed on a clear framework. The EU Data Act’s switching rules, effective since September 2025, cover inputs and outputs, but it remains unclear if chatbots qualify as 'data processing services.' Meanwhile, ChatGPT has been flagged as a potential gatekeeper under the Digital Markets Act, which could force real-time data portability if officially designated. In the US, there are no specific laws addressing chatbot portability, leaving the burden entirely on developers to build their own escape hatches.

Key Takeaways

  • Configuration files like AGENTS.md are becoming standardized and portable, but memory and chat history remain deeply siloed by proprietary formats.
  • There are no APIs for reading or writing AI memory across major platforms, forcing users to rely on error-prone manual transfers.
  • The open-source memory ecosystem is growing rapidly but suffers from high churn, with notable projects like ByteRover already archiving.
  • Regulatory frameworks like the EU Data Act are in effect, but their application to AI chatbots and their inferred memories is still legally ambiguous.

The Bottom Line

Stop trusting your context to the cloud. Until standards for memory export are enforced, only the data you keep in local, plain-text files is truly yours. If you aren't actively exporting your agent's memory to a git-backed Markdown store today, you're building your workflow on a rented foundation that can be evicted with a single API change.