Redis Iris combines agent routing, observability and resilient messaging
Redis expanded its Iris context engine into a six-part agent layer: routing, playbooks, memory and the context gateway are generally available, while Lens and Agent Mesh are in beta.
AT A GLANCE
Key points
- Four Iris components are generally available; Lens and Agent Mesh are in beta.
- Lens traces how context entered the prompt step by step.
- Agent Mesh is designed to resume agent streams after interruptions.
What is changing?
On November 4, Redis expanded Iris with six composable capabilities. Intent Router, Agent Playbooks, Agent Memory and Context Gateway are generally available, while Lens and Agent Mesh are offered in beta. The company says the components can be used together or independently.
Intent Router sends requests to a target based on semantic intent; Playbooks retrieves published procedures; Memory preserves state across sessions; and Context Gateway provides a common access point for MCP tools and Redis data. Lens traces which context entered the prompt behind an agent response.
Agent Mesh is intended to let streams resume after dropped connections and prevent duplicate operations. These are provider claims; production teams should validate the resilience of the beta components, the data scope of traces and the impact of routing errors under their own workloads.
Explore the original sources
Source date: 4 November 2026.
Published by AI Radar: 4 Nov 2026, 21:08 (Istanbul, UTC+3).
FOLLOW THE TOPIC
Topics and tags
Share your discovery.
Send this story to a friend.
Reader comments
What do you think about this development? Share your experience or question. Comments are published after editorial approval.
Your name/nickname and comment become public if approved. Read: Privacy notice.
Loading comments…