Redis launches Context Engine for AI agent memory

SiliconANGLE reports that Redis launched the Context Engine, a three-part memory layer for enterprise AI agents consisting of Redis Context Retriever, Redis Agent Memory, and Redis Data Integration. According to SiliconANGLE, Redis Data Integration is made generally available on May 18, 2026, while Redis Context Retriever and Redis Agent Memory are offered in preview. SiliconANGLE reports Redis frames the product as a response to what it calls the "context problem," which the company links to hallucinations and stalled workflows when agents cannot access or stitch together relevant business data.

According to SiliconANGLE, the Context Retriever creates a semantic model of business data so agents can map relationships such as how a customer relates to an opportunity or support ticket. The article reports the retriever automatically generates the tools agents need to fetch data using the open-source Model Context Protocol. SiliconANGLE describes Agent Memory as a dual-layered state manager that keeps short-term interaction history while maintaining a more durable, long-term memory cache. The coverage also characterizes Redis Data Integration as the connector layer that links agents to systems like CRM, shipping databases, and document stores.

Companies building multi-source agent workflows commonly struggle with brittle, ad hoc integrations and text-to-SQL approaches that break as schemas and prompts evolve. A dedicated context layer that provides semantic retrieval and persistent agent state can reduce developer work to maintain connectors and lower the incidence of retrieval-induced hallucinations.

watch for integration patterns and performance metrics as enterprises pilot the Context Engine, specifically retrieval latency, vector store consistency, memory eviction policies, and the fidelity of mappings produced by the Model Context Protocol. Observers will also look for third-party tools and connectors that target common enterprise systems to evaluate how much integration effort the product actually removes.