--- title: 'End the Session Context Wars: Introducing session.llmfeed.json' description: >- A revolutionary open standard for AI session context that puts users back in control and ends vendor lock-in author: WellKnownMCP Team date: '2025-06-13' lastmod: '2025-06-13' type: news categories: - advocacy - standards - session-management tags: - ai-platforms - data-ownership - interoperability - open-standards - session.llmfeed.json - user-control - vendor-lock-in audience: - developer - business - ai-platform-vendors - users priority: high riskLevel: low updateFrequency: static pageType: advocacy interactionComplexity: moderate slug: end-session-context-wars-session-llmfeed canonical_url: 'https://wellknownmcp.org/news/end-session-context-wars-session-llmfeed' mcpFeedUrl: /.well-known/mcp.llmfeed.json keywords: - session context - AI memory - vendor lock-in - interoperability - open standards - data ownership - ChatGPT memory - Claude projects autoDiscoverFeeds: true agentReadiness: true llmBehaviorHints: advocacy-focused feedTypes: - session - mcp - capabilities capabilities: - session_context_export - cross_platform_import - user_controlled_memory contentFeatures: - technical-specification - code-examples - call-to-action - advocacy-messaging - industry-analysis strategicImportance: critical innovationLevel: revolutionary industryImpact: transformative standardsRelevance: foundational trackingCategories: - advocacy-content - session-standards - vendor-response - community-adoption --- # End the Session Context Wars: Introducing `session.llmfeed.json` *Published: June 13, 2025 | Author: WellKnownMCP Team* --- ## The Problem: AI Memory Silos Are Breaking User Experience We're living through the **great AI memory fragmentation**. Every major AI platform has built their own proprietary session memory system: - **ChatGPT Memory**: Locked into OpenAI's ecosystem - **Claude Projects**: Trapped in Anthropic's garden - **Gemini Workspace**: Google's closed loop - **Copilot Context**: Microsoft's walled garden **The result?** Users are forced to: - ❌ Recreate context manually when switching platforms - ❌ Stay locked into one system despite better alternatives elsewhere - ❌ Lose valuable project history when platforms change or fail - ❌ Accept whatever memory model each vendor decides to impose This is **vendor lock-in disguised as innovation**. It's time for a better way. --- ## The Solution: Open Session Context Standard Today, we're proposing `session.llmfeed.json` – an **open, interoperable standard** for AI session context that puts users back in control. ### What is `session.llmfeed.json`? A structured, user-controlled file that captures session context in a platform-agnostic format: ```json { "feed_type": "session", "metadata": { "title": "My AI Project Context", "origin": "user-controlled", "created_at": "2025-06-13T15:30:00Z", "expires_at": "2026-06-13T15:30:00Z" }, "session": { "context_summary": "Working on wellknownmcp.org improvements...", "user_preferences": { "communication_style": "technical but enthusiastic", "output_format": "detailed with examples", "expertise_level": "advanced" }, "project_state": { "current_phase": "specification finalization", "key_decisions": [ "Human/Agent toggle approved for v2.0", "Priority: spec > site > llmca > llmfeedforge" ], "pending_items": [ "Complete LLMFeed specification", "Deploy LLMCA certification system" ] }, "conversation_patterns": { "established_facts": [ "User prefers React + TypeScript examples", "Project uses MCP standards throughout" ], "recurring_themes": ["interoperability", "open standards"] } }, "instructions": { "behavior_hint": "Maintain project continuity and technical depth", "update_policy": "user_explicit_only", "sharing_scope": "private" }, "trust": { "user_consent": "explicit", "data_ownership": "user_controlled", "exportable": true, "revocable": true, "retention_policy": "user_defined" } } ``` --- ## Why This Changes Everything ### 🔓 **User Ownership vs Platform Control** **Current State:** ``` User context → ChatGPT Memory → OpenAI servers → Black box User context → Claude Projects → Anthropic servers → Limited access User context → Gemini → Google servers → Vendor lock-in ``` **With session.llmfeed.json:** ``` User context → session.llmfeed.json → User's control → Universal portability ``` ### 🔄 **Universal Interoperability** One context file works everywhere: ```bash # Same context, any platform claude --import session.llmfeed.json "Continue our project discussion" chatgpt --context session.llmfeed.json "Pick up where we left off" gemini --session session.llmfeed.json "Resume our collaboration" ``` ### 👤 **Transparent User Control** Users can: - ✅ **Read** their context (human-readable JSON) - ✅ **Edit** what gets remembered (direct file modification) - ✅ **Export** to any platform (no vendor lock-in) - ✅ **Delete** completely (true right to be forgotten) - ✅ **Audit** what's being shared with AI systems --- ## The Technical Benefits ### For AI Platforms **Competitive Advantage Through Openness:** - Easier user onboarding (import from competitors) - Reduced development cost (standard vs custom memory systems) - Enhanced user trust (transparency over black boxes) - Innovation focus on AI capabilities, not data lock-in tactics ### For Developers **Standard Integration:** ```javascript // Universal session loading import { loadSessionContext } from 'llmfeed-session' const context = await loadSessionContext('session.llmfeed.json') await aiPlatform.initialize({ context }) ``` ### For Enterprise **Compliance & Governance:** - Auditable AI interactions - Data residency control - Session context portability - Standardized AI governance policies --- ## The Ecosystem We're Building ### Phase 1: Standard Definition ✅ - [LLMFeed specification](https://wellknownmcp.org/spec/) extended with session type - Reference implementation and validation tools - Community feedback integration ### Phase 2: Tooling & Adoption 🚀 - Browser extensions for session export/import - CLI tools for context management - Integration libraries for popular platforms ### Phase 3: Platform Integration 🎯 - Native support in AI platforms - Automatic session.llmfeed.json generation - Seamless cross-platform experience --- ## Real-World Impact ### For Individual Users *"I can finally switch between AI platforms without losing my project context. My data, my control."* ### For Businesses *"We maintain our AI conversation history in standardized, auditable formats that meet our compliance requirements."* ### For Developers *"Building AI applications is easier when I don't have to integrate with 5 different proprietary memory APIs."* ### For the AI Industry *"Competition based on AI capabilities, not data lock-in tactics. Innovation thrives."* --- ## The Path Forward ### For AI Platform Vendors **Join the movement.** Be the first to support `session.llmfeed.json` natively and gain competitive advantage through user empowerment rather than lock-in. ### For Developers **Start building.** Integrate session context import/export in your AI applications. Show users you respect their data ownership. ### For Users **Demand better.** Ask your AI platforms: *"When will you support open session context standards?"* --- ## Technical Implementation ### Basic Session Export ```bash # User-initiated context capture "Please generate a session.llmfeed.json with our current project context" # Result: Structured file ready for portability ``` ### Cross-Platform Import ```bash # Universal context loading "Import context from session.llmfeed.json and continue our discussion" # Works on any supporting platform ``` ### Privacy-First Design ```json { "trust": { "user_consent": "explicit", "data_minimization": true, "purpose_limitation": "session_continuity_only", "retention_policy": "user_controlled" } } ``` --- ## Join the Standard ### Implementation Resources - 📘 [Session LLMFeed Specification](https://wellknownmcp.org/spec/02_llmfeed_feedtype/llmfeed_feedtype_session) - 🛠️ [Reference Implementation](https://github.com/wellknownmcp/llmfeed-spec) - 🧪 [Validation Tools](https://wellknownmcp.org/llmfeedhub) ### Community - 💬 [GitHub Discussions](https://github.com/wellknownmcp/llmfeed-spec/discussions) --- ## The Choice Is Clear Continue accepting fragmented, proprietary memory systems that lock you in... **Or embrace open standards that put you in control.** The future of AI interaction shouldn't be determined by which platform happened to remember your context. It should be determined by which AI gives you the best results with **your** data under **your** control. `session.llmfeed.json` makes this future possible. --- ## Call to Action **AI Platform Vendors:** Implement native `session.llmfeed.json` support and lead the industry toward user empowerment. **Developers:** Build session context portability into your applications from day one. **Users:** Vote with your usage. Choose platforms that respect your data ownership. **Everyone:** Help us end the session context wars once and for all. --- *The agentic web thrives on open standards, interoperability, and user control. Session context should be no different.* **Ready to take control of your AI context?** [Learn more about session.llmfeed.json →](https://wellknownmcp.org/spec/02_llmfeed_feedtype/llmfeed_feedtype_session) --- ## About WellKnownMCP WellKnownMCP.org is building the open standards that power the agentic web. From structured content feeds to cryptographic trust systems, we're creating the infrastructure that makes AI interactions transparent, portable, and user-controlled. [Learn more](https://wellknownmcp.org/) | [GitHub](https://github.com/wellknownmcp) | [Contribute](https://wellknownmcp.org/contribute)