RC/AI: Context Retriever#3336
Merged
Merged
Conversation
Contributor
Contributor
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
mich-elle-luna
approved these changes
May 15, 2026
Collaborator
mich-elle-luna
left a comment
mich-elle-luna
left a comment
There was a problem hiding this comment.
thank you! just a typo and a question.
|
|
||
| - Enter the field name in the **Field** cell. | ||
| - Select the **PK** checkbox if the field is a primary key. You must have at least one primary key. | ||
| - If the field is related to any other defined entities, select it from the **Related Entity** dropdown. This is usually set if the field contains primary keys of another entity. For example, you might have an |
Collaborator
There was a problem hiding this comment.
Suggested change
| - If the field is related to any other defined entities, select it from the **Related Entity** dropdown. This is usually set if the field contains primary keys of another entity. For example, you might have an | |
| - If the field is related to any other defined entities, select it from the **Related Entity** dropdown. This is usually set if the field contains primary keys of another entity. |
|
|
||
| ## Overview | ||
|
|
||
| Production agents fail not because the model is wrong, but because the context layer breaks. Enterprise data can be fragmented across multiple different databases, and can be disorganized. Teams try to patch this with text-to-SQL, OpenAPI-to-MCP wrappers, or hand-built tools — which works for demos but creates tool zoo sprawl, SQL risk, and agents that can't reliably choose the right path in production. Redis Context Retriever gives teams a governed, schema-first surface agents can traverse safely. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Production agents fail not because the model is wrong, but because the context layer breaks. Enterprise data can be fragmented across multiple different databases, and can be disorganized. Teams try to patch this with text-to-SQL, OpenAPI-to-MCP wrappers, or hand-built tools — which works for demos but creates tool zoo sprawl, SQL risk, and agents that can't reliably choose the right path in production. Redis Context Retriever gives teams a governed, schema-first surface agents can traverse safely. | |
| Production agents fail not because the model is wrong, but because the context layer breaks. Enterprise data can be fragmented across multiple different databases, and can be disorganized. Teams try to patch this with text-to-SQL, OpenAPI-to-MCP wrappers, or hand-built tools — which works for demos but creates tool sprawl, SQL risk, and agents that can't reliably choose the right path in production. Redis Context Retriever gives teams a governed, schema-first surface agents can traverse safely. |
| To create a Redis Context Retriever service, you will need a Redis Cloud database that already has relevant data. If you don't have one, see [Create a database]({{< relref "/operate/rc/databases/create-database" >}}). If your source data lives in a relational database, use [Redis Data Integration (RDI)]({{< relref "/operate/rc/databases/rdi" >}}) to ingest it into a Redis Cloud database first. | ||
|
|
||
| {{< note >}} | ||
| Agent Memory does not support the following databases during public preview: |
Collaborator
There was a problem hiding this comment.
Should this be a note about context retriever?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the best I can possibly do before Monday.
Note
Low Risk
Documentation-only changes that add new pages and adjust sidebar ordering; low risk aside from potential broken links/typos in new docs.
Overview
Adds a new Redis Context Retriever doc section, including a
/developoverview page and new/operate/rcguides for creating a service, viewing services, and managing admin keys, plus a shared get-started embed.Reorders Context Engine sidebar positioning by updating
_index.mdweightvalues forLangCache,Agent Memory, and the newContext Retrieverentry.Reviewed by Cursor Bugbot for commit 7d00849. Bugbot is set up for automated code reviews on this repo. Configure here.