docs(google-adk): bring ADK docs to parity with adk-redis 0.0.9

[nkanu17]

The redis.io Google ADK pages were written against adk-redis 0.0.5. Since then 0.0.7 added selectable memory backends, 0.0.8 renamed the session service, and 0.0.9 raised the managed SDK floor and added cache entry IDs. This brings all five pages to 0.0.9, which is the version currently on PyPI.

Following review, the pages now also centre on Redis Agent Memory and quarantine the deprecated opensource-agent-memory backend on its own page.

Correction to an earlier version of this PR

An earlier revision of this description, and my comment of Aug 3, claimed that auto-summarization and extraction strategies were Agent Memory Server only. That was wrong, and the claim has been removed from the pages.

Redis Agent Memory supports both, on Redis Cloud and self-managed:

• Extraction strategies discrete, summary, preferences, and custom, per Agent Memory.
• Automatic summarization, configurable per service, per Create an Agent Memory service.

The mistake was reading an adk-redis config surface as a product capability. model_name and context_window_max are Agent Memory Server passthroughs in adk-redis, but the managed service does this work configured at the service level instead. Of the four capabilities I originally listed, only recency-weighted search (adk-redis's semantic_weight / recency_weight) and the MCP endpoint are genuinely Agent Memory Server only.

Thanks @mich-elle-luna, whose suggested wording on _index.md caught this.

Functional breakage fixed

Two of these were not just stale wording; readers copying the samples would hit failures.

• The quick start could not reach a local memory server. 0.0.7 made redis-agent-memory the default backend, but every sample passed a localhost Agent Memory Server URL with no backend override, so the services silently targeted the Data Plane. All samples now set backend explicitly.
• create_memory_mcp_toolset no longer exists in adk-redis. The MCP samples imported it, so they raised ImportError. The MCP path now uses ADK's native McpToolset + SseConnectionParams, matching the fitness_coach_mcp example, and lives on the deprecated page since no managed equivalent exists.
• RedisWorkingMemorySessionService was renamed to RedisSessionMemoryService in 0.0.8. The old name is a deprecated alias that emits a DeprecationWarning and is removed in 0.1.0. All samples use the new name, with a note covering the alias and the moved module path.

Config tables corrected

The documented defaults did not match the code:

Parameter	Was documented	Actual
recency_boost	False	True
extraction_strategy	None	discrete (plus a fourth value, custom)
semantic_weight / recency_weight	0.7 / 0.3	0.8 / 0.2
api_base_url, default_namespace	Required	Both have defaults

Also added the missing backend, api_key, store_id, timeout, threshold, weight, and half-life fields.

Structure

Per @mich-elle-luna's review, the deprecated backend no longer runs through the main pages:

• agent-memory-server.md is new, carries a deprecation banner, and holds the Docker setup, the backend-only config, the MCP path, migration steps, and the examples still on that backend.
• The four supported pages cover Redis Agent Memory only, each with a single pointer to the deprecated page.
• Redis Agent Memory is documented as one backend with two deployments, Redis Cloud and self-managed, selected by api_base_url rather than by backend, linking @n-valchev's self-managed pages and the Redis Cloud create-service guide.

Other changes

• Documented all six memory tools. GetMemoryTool and MemoryPromptTool were missing.
• Documented invocation-user resolution from tool_context and the client-supplied id on CreateMemoryTool (0.0.9).
• Semantic caching: cache entry IDs, CacheEntry, delete_by_id() targeted invalidation (0.0.9), and the required server_url on LangCacheProviderConfig.
• Examples: nine to ten, added managed_memory_quickstart, and noted the runner per example (python main.py vs adk web .). redis_search_tools wires three tools, not four.
• Noted the redis-agent-memory>=0.2.0 floor.

Verification

Every class name, config field, default value, and example was checked against adk-redis main at 0.0.9 rather than against the changelog. Product capability claims are checked against the Agent Memory docs in this repo, which is what the correction above came from.

Links use relref rather than absolute URLs, so if @raphaeldelio moves the self-managed content to /operate the build fails loudly instead of leaving dead links. All 44 relref targets across these pages resolve to existing content files.

I could not get a clean local Hugo build: the same ByWeight template error reproduces on an unmodified main with Hugo 0.160.1, so it is a local version mismatch rather than anything in this change. Worth a look at the CI build.

Still open, outside this PR

• Examples on the deprecated backend. Four of five memory examples default to opensource-agent-memory. They live in adk-redis, so redis.io can only label them. fitness_coach_mcp cannot move at all, since MCP has no managed equivalent.
• Migration guide or tool, as @mich-elle-luna suggested. The page has migration steps for the adk-redis config change, but a real Agent Memory Server to Data Plane data-migration path needs product input rather than anything I can infer.
• Car dealership tutorial, linked from these pages, still uses RedisWorkingMemorySessionService with no backend field. It lives outside this repo.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only changes to integration guides; no application code or runtime behavior in this repo.

Overview
Brings the Google ADK integration docs in line with adk-redis 0.0.9 (selectable backends, session service rename, cache entry IDs, redis-agent-memory>=0.2.0). Redis Agent Memory (backend="redis-agent-memory") is now the default path for new work on Redis Cloud or self-managed deployments, chosen via api_base_url, api_key, and store_id instead of local Agent Memory Server Docker setup.

Adds agent-memory-server.md for the deprecated opensource-agent-memory backend with migration steps, backend-only config, and MCP notes; supported pages no longer treat MCP as a first-class pattern. Samples and tables use RedisSessionMemoryService, explicit backend, and updated config defaults/fields; documents six REST memory tools, invocation-scoped users, and semantic cache CacheEntry / delete_by_id() plus LangCache server_url. Examples page promotes managed_memory_quickstart and separates three legacy examples.

^{Reviewed by Cursor Bugbot for commit 6545386. Bugbot is set up for automated code reviews on this repo. Configure here.}

[CLAassistant]

All committers have signed the CLA.

[mich-elle-luna]

Hi @nkanu17 thank you for this update, last week @n-valchev documented the self-hosted installation of agent memory here, https://redis.io/docs/latest/develop/ai/context-engine/agent-memory/self-managed/

Please update this PR to refer to those new pages instead of the deprecated agent server pages and repo (or in addition to that). Also just fyi, @raphaeldelio is thinking of moving all that self-managed content Nikolay published last week to the /operate section, so you all should coordinate potentially if he does to ensure that link targets are updated. Thank you!

[mich-elle-luna]

Looking good, just need to add references to https://redis.io/docs/latest/develop/ai/context-engine/agent-memory/self-managed/ and related content.

[nkanu17]

Thanks @mich-elle-luna, updated in 51c7df9.

Acting on this surfaced something bigger than a missing link, so flagging it explicitly for you and @n-valchev.

These pages presented a binary: managed means redis-agent-memory, self-hosted means opensource-agent-memory. That framing is wrong, and combined with the deprecation label it would have actively steered anyone wanting to run Agent Memory themselves toward the deprecated backend.

Self-managed Agent Memory serves the same shared Data Plane API as Redis Cloud (/v1/stores/{storeId}/..., per the self-managed API examples), and adk-redis builds its client as _AgentMemory(api_base_url, api_key=..., store_id=...) with the base URL as a positional argument, so it is not Redis Cloud specific. That means three deployment paths across two backend values:

Deployment	backend	api_base_url
Redis Cloud	redis-agent-memory	Redis Cloud Agent Memory endpoint
Self-managed	redis-agent-memory	Your own Data Plane URL
Agent Memory Server (deprecated)	opensource-agent-memory	Your server URL

You pick a deployment with api_base_url, not with backend. So the pages now:

• Add a deployment table mapping each path to its backend, api_base_url, and setup guide, linking Nikolay's self-managed pages and the Redis Cloud create-service page.
• Add a note warning against reaching for opensource-agent-memory just because a deployment is self-hosted. The two are different systems, not two deployments of one system.
• Change the feature matrix columns from "Managed vs Self-hosted" to the two backends, since the differences follow the backend. Self-managed has the same feature set as Redis Cloud.
• Retire "self-hosted" as a synonym for opensource-agent-memory across all five pages, because self-managed Agent Memory is also self-hosted.

On the /operate coordination with @raphaeldelio: I used relref rather than absolute URLs throughout, so if the self-managed content moves, the Hugo build fails loudly instead of leaving dead links. Verified all 20 relref targets on these pages resolve.

One thing worth a second opinion: the feature matrix still shows recency-boosted search, auto-summarization, extraction strategies, and MCP as Agent Memory Server only. I framed that as current state plus a migration-timing consideration, but if there is a roadmap or support timeline for those on the Data Plane API, that wording should say so rather than implying the gap is permanent.

[mich-elle-luna]

Hi Nitin, thank you for these updates. Unfortunately, I think this is really confusing with the old deprecated content still weaved into the new info. So, my feedback is to separate or keep all the old info in a section or file that is marked deprecated with a banner, and provide only the info for the supported services that will be maintained going forward in these main files (removing or moving content that really no longer applies. But, I can be persuaded otherwise , if you have perspectives from others that this content must live side-by-side. Thanks!

[mich-elle-luna]

move or remove

[mich-elle-luna]

move or remove

[mich-elle-luna]

move or remove

[mich-elle-luna]

move or remove

[mich-elle-luna]

move or remove

[nkanu17]

Hi Nitin, thank you for these updates. Unfortunately, I think this is really confusing with the old deprecated content still weaved into the new info. So, my feedback is to separate or keep all the old info in a section or file that is marked deprecated with a banner, and provide only the info for the supported services that will be maintained going forward in these main files (removing or moving content that really no longer applies. But, I can be persuaded otherwise , if you have perspectives from others that this content must live side-by-side. Thanks!

Sounds good, thanks for the review!
Will make some changes and tag you again

[nkanu17]

Correction to my Aug 3 comment, flagging it rather than quietly editing since @n-valchev was tagged on it.

I claimed auto-summarization and extraction strategies were Agent Memory Server only. That was wrong. Redis Agent Memory supports both, on Redis Cloud and self-managed:

• Extraction strategies discrete, summary, preferences, custom — Agent Memory
• Automatic summarization, configurable per service — Create an Agent Memory service

I had read an adk-redis config surface as a product capability. model_name and context_window_max are Agent Memory Server passthroughs in adk-redis, while the managed service does that work configured at the service level. Of the four capabilities I listed, only recency-weighted search (adk-redis's semantic_weight / recency_weight) and the MCP endpoint are genuinely Agent Memory Server only.

@mich-elle-luna your suggested wording on _index.md is what caught this, and it's what the page now uses. The feature matrix that carried the bad claim is gone, replaced by the support-level split you asked for, so the error is not in the current diff. The PR description is updated too.

That also removes my "second opinion" question from the earlier comment. I was asking about a roadmap to close a gap that mostly did not exist.

On the restructure: agent-memory-server.md now holds the Docker setup, backend-only config, the MCP path, migration steps, and the examples still on that backend, behind a deprecation banner. The four supported pages point to it once each. Ready for another look when you have time.

Two of your asks are genuinely outside this repo, so flagging rather than silently dropping them:

• Examples. Four of five memory examples default to opensource-agent-memory and live in adk-redis. redis.io can only label them; moving them to the default backend is a change there. fitness_coach_mcp cannot move at all, since MCP has no managed equivalent.
• Migration guide/tool. The new page covers the adk-redis config change, but a real Agent Memory Server to Data Plane data-migration path needs product input. Happy to write it if someone can tell me what the supported path is.

[mich-elle-luna]

thank you! just one small change for clarity

[nkanu17]

thank you! just one small change for clarity
@mich-elle-luna
Thanks, I signed the cla agreement as well