[LI (ktz03)]

Motivation & Context

The Redis context-provider sample guide still documents removed configuration names and the old invoking hook. Its optional OpenAI-key instructions also conflict with examples that instantiate OpenAITextVectorizer.

Description & Review Guide

• What are the major changes? Align one sample README with redis_vectorizer, overwrite_index, the before_run/after_run hooks, and the existing examples' embedding prerequisites. Distinguish context retrieval from complete conversation-history persistence.
• What is the impact of these changes? Documentation only. Full-text and hybrid constructor/schema configurations were checked locally, together with the eight constructor calls in the three unchanged context samples. Live Redis, OpenAI/Foundry calls and the full sample suite were not run.
• What do you want reviewers to focus on? Whether the configuration and setup instructions accurately match the existing provider and examples.

Related Issue

N/A - trivial change: correct stale API names and setup instructions in one README; no runtime or public API changes.

AI Assistance

• No material AI assistance was used.
• This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

AI assistance details: Documentation, API checks, and PR description.

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" in the title prefix).

[Copilot]

🟡 Changes recommended

The prerequisites still omit an embedding-dependent scenario, leaving readers without setup instructions needed to run it.

2 open findings

• Correct cross-session retrieval claim to context retrieval across turns · New
• Document OpenAI API key prerequisite for multiple-agents scenario · New

What changed in this PR

Updates the Redis context-provider sample guide to match current APIs and embedding requirements. No runtime code changes.

Changes:

• Replaces obsolete configuration names and lifecycle hooks.
• Clarifies OpenAI embedding prerequisites.
• Distinguishes context retrieval from complete conversation-history persistence.

File	Description
python/​samples/​02-agents/​context_providers/​redis/​README.md	Updates API guidance, setup requirements, and sample descriptions.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[Eduard van Valkenburg (eavanvalkenburg)]

LI (@ktz03), the setup still installs only agent-framework-redis, but all three context samples import FoundryChatClient, which requires the separate agent-framework-foundry distribution. Neither Redis nor its core dependency installs that connector, so following this guide in a fresh environment fails at import before reaching the corrected configuration. Please include agent-framework-foundry in the installation command.

[LI (ktz03)]

Added agent-framework-foundry to the Redis sample installation command in fc9b861. The three context samples import FoundryChatClient from that separate connector.