Skip to content

Link search and RAG pages to the AI agent builder - #3804

Open
mich-elle-luna wants to merge 2 commits into
mainfrom
ai-builder-links
Open

Link search and RAG pages to the AI agent builder#3804
mich-elle-luna wants to merge 2 commits into
mainfrom
ai-builder-links

Conversation

@mich-elle-luna

@mich-elle-luna mich-elle-luna commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Add pointers from the high-traffic search and RAG pages to the AI agent builder, telling readers to choose the Knowledge Assistant template to generate a working RAG agent built on Redis vector search:

  • Redis Search overview: a next-step list item (the page already has other callouts, so this avoids stacking a third box)
  • Vector search concepts: appended to the intro
  • Vector search how-to and the RAG quick start: a tip callout each

The Redis Agent Memory pages are deferred: they should point at the Redis Iris Conversational Assistant template, which ships with a separate PR.


Note

Low Risk
Markdown-only navigation and copy changes with no runtime or API impact.

Overview
Documentation cross-links steer readers from high-traffic search and RAG content toward the [AI agent builder]({{< relref "/develop/ai/agent-builder" >}}) and the Knowledge Assistant template for a working RAG agent on Redis vector search.

On the Redis Search overview, a new numbered next-step item joins the existing list (instead of another callout). Vector search concepts extends the intro paragraph with the same pointer. The vector search how-to and RAG with Redis pages each get a tip callout describing ingestion, hybrid retrieval, and citations where relevant.

Reviewed by Cursor Bugbot for commit 3dbfd62. Bugbot is set up for automated code reviews on this repo. Configure here.

Add pointers from the high-traffic search and RAG pages to the AI agent
builder, telling readers to choose the Knowledge Assistant template to
generate a working RAG agent built on Redis vector search:

- Redis Search overview: a next-step list item (the page already has other
  callouts, so this avoids stacking a third box)
- Vector search concepts: appended to the intro
- Vector search how-to and the RAG quick start: a tip callout each

The Redis Agent Memory pages are deferred: they should point at the Redis
Iris Conversational Assistant template, which ships with a separate PR.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mich-elle-luna
mich-elle-luna requested a review from a team August 12, 2026 22:21
@github-actions

github-actions Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

🧠 Redis Memory

Found 7 related items from repository history (2 new this commit):

Memory updated at 3dbfd62

@andy-stark-redis andy-stark-redis left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An issue to think about (maybe for the whole team), but basically LGTM.

A vector search query on a vector field allows you to find all vectors in a vector space that are close to a given vector. You can query for the k-nearest neighbors or vectors within a given radius.

{{< tip >}}
Want a working example instead of building from scratch? Open the [AI agent builder]({{< relref "/develop/ai/agent-builder" >}}) and choose the **Knowledge Assistant** template to generate a complete RAG agent that uses the vector search queries described here.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A tersely worded question like this isn't our usual style but it is the kind of thing that AI often generates now. It's a matter of whether we're going to try to "correct" stuff like this (to teach AI how we prefer to express these things) or whether we're just letting this go now. Same basic issue applies with two of the other changed files, btw.

Drop the rhetorical "Want.../Prefer..." hooks and marketing phrasing,
lead with the task/goal, and use direct present-tense imperative.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants