I’d like to propose a feature that could significantly improve the future of AI APIs and developer workflows.
Today, nearly all major AI APIs are fundamentally stateless. Developers must continuously resend conversation history, summaries, project state, memory objects, and large JSON payloads with every request. This increases token costs, latency, complexity, and engineering overhead.
Proposal: Open Context Protocol (OCP)
A native protocol that allows models to maintain and access persistent context across API requests through a dedicated Context ID.
Example:
context_id: project_8f29x4
Instead of resending thousands of tokens every request, developers could simply reference an existing context.
Core Capabilities
-
Persistent project memory across API calls.
-
Native context retrieval without manually resending chat history.
-
Automatic context compression and optimization by the model.
-
Cross-session continuity.
-
Context branching and versioning.
-
Shared project memory for multi-agent systems.
-
Optional access to relevant context from previous conversations and projects.
Advanced Vision
A future OCP implementation could become an industry-standard format supported across multiple AI providers.
For example:
-
OpenAI
-
Google
-
Anthropic
-
xAI
-
DeepSeek
could agree on a portable context format:
ocp://project/8f29x4
allowing users to continue work between different AI ecosystems without losing project understanding, goals, decisions, architecture, and historical reasoning.
Why This Matters
For high-end developer tools, creative applications, IDEs, automation systems, and long-running AI projects, persistent context is often more valuable than larger context windows.
Developers shouldn’t need to repeatedly transmit the same history, state, and metadata thousands of times. The model should be capable of maintaining a structured, optimized understanding of a project and retrieving it when needed.
In my opinion, a native persistent context system such as Open Context Protocol (OCP) could become as important to AI systems as HTTP became to the web.