Redis Broadens Iris With Agent Routing, Observability and Messaging

Redis announced on November 4, 2026 that its Iris real-time context engine now offers six composable capabilities for AI agents, with four generally available and two in beta. The expansion adds request routing, reusable procedures, observability and resilient messaging to a product previously centered on context and memory.

Customers can use the capabilities together, independently or in any combination within one runtime. Rowan Trollope’s rationale is that developers should not have to assemble separate infrastructure products to give agents memory, relevant context, live data access, routing and communication. Redis’s getting-started offer includes 5,000 free messages.

A companion technical deep dive by Simba Khadder, Redis’s director of software engineering, describes the production problems that design is meant to address: agents starting without prior history, retaining sensitive details while losing useful preferences, working with incomplete information and repeatedly rebuilding context for requests they have already handled. Those failure modes connect the release’s otherwise separate features around continuity, reuse and control.

Four Capabilities Are Generally Available

Intent Router matches a request’s meaning rather than its exact wording, then directs it to a remembered FAQ, an agent skill, a human or an LLM. It also supports agent and model routing, guardrails and fuzzy conditional decisions, allowing differently phrased versions of the same request to be handled as the same underlying problem.

Agent Playbooks separates stable answers that can be reused from requests that need current data and a fresh run of a known procedure. Redis said the playbooks become more thorough and accurate with repeated use, cutting resolution times and token spending. That makes Playbooks the reuse counterpart to Intent Router: one identifies the kind of request, while the other determines whether an existing answer or procedure can satisfy it.

Agent Memory uses MemoryETL to build memories from user actions, documents, knowledge bases and other semi-structured data. It organizes those memories hierarchically for finer-grained control and provides inspection, audit and provenance features so teams can see where each memory came from. It can also discard information it should not retain, including personally identifiable information.

Context Gateway provides one governed entry point to connected context sources. Customers can bring their own MCP servers, cache which tools solve particular problems and build reusable results for consistency across sessions. Redis presents tool caching as a way to reduce token use, extending the release’s emphasis on avoiding repeated model work from answers and procedures to data access.

Beta Tools Cover Auditing and Connection Failures

Lens traces an agent outcome to the skill, route or FAQ that served it, the memory used and the originating session. It also exposes task success, tokens per task and latency, pairing an audit trail with operational measurements. The result is intended to make agent behavior queryable when teams need to diagnose a wrong answer, investigate token consumption or establish why an action occurred.

Agent Mesh addresses communication interruptions. Agents communicate over ephemeral streams, with automatic buffering and reconnection when connections drop. Durable SSE Streams are designed to keep responses flowing through interruptions, while A2A Comms supplies a channel for agent delegation and handoffs. Lens and Mesh therefore cover distinct production risks: reconstructing a decision and preserving a conversation.

From May Launch to Customer Use

Redis introduced Iris on May 18, 2026 as a context and memory layer between an agent and the data it needs. That launch combined Context Retriever, Agent Memory, Redis Data Integration, LangCache and Redis Search, with Context Retriever and Agent Memory in preview. Agent Memory has since moved to general availability, while the new lineup extends the original retrieval-and-memory emphasis into routing, repeatable procedures, decision tracing and stream recovery.

Safe in Home senior software developer Nick Thompson described a concrete deployment on the Redis Iris product page: “Redis Agent Memory helps us store and reuse context across our coding agents in real time.” His team uses it to capture engineering decisions, bug details and development context as agents work, keeping the information available across the team instead of losing it between sessions or tools. A service also reads from and writes to that memory while monitoring the company’s API, then files bug reports in its ticketing system in real time.

The release consequently broadens Iris’s role from supplying context to coordinating how an agent handles a request, reuses prior work, remembers selected information and reaches governed data. Its maturity is uneven, though: those operational foundations are generally available, while the decision-auditing and connection-recovery layers remain in beta.