Skip to content

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

Open
mich-elle-luna wants to merge 1 commit into
mainfrom
ai-builder-links
Open

Link search and RAG pages to the AI agent builder#3804
mich-elle-luna wants to merge 1 commit 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
Documentation-only cross-links with no runtime, API, or configuration changes.

Overview
This PR adds cross-links from high-traffic Redis Search and RAG docs to the [AI agent builder]({{< relref "/develop/ai/agent-builder" >}}), steering readers to the Knowledge Assistant template for a ready-made RAG app on Redis vector search.

On the Redis Search overview, a new next steps list item points to the builder (instead of another callout box, since the page already has alert/tip blocks). Vector search concepts extends the intro paragraph with the same pointer. The vector search how-to and RAG with Redis quick start each get a tip callout describing ingestion, hybrid retrieval, and citations where relevant.

Copy is consistent across pages: open the agent builder and choose Knowledge Assistant. Agent Memory → Conversational Assistant links are intentionally out of scope for this PR.

Reviewed by Cursor Bugbot for commit c6eff08. 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

Copy link
Copy Markdown
Contributor

🧠 Redis Memory

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

Memory updated at c6eff08

@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.

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