docs(managed_agents): link Memory cookbook to Agent Memory docs

[gaganb-ant]

Small polish pass on the Memory cookbook (CMA_remember_user_preferences.ipynb):

• Hyperlinked "Memory" in the intro paragraph to the Agent Memory docs so readers can jump straight to the reference.
• Updated the "Memory stores API reference" link in the Learn More section to the same platform.claude.com URL.
• Removed the "Other notebooks in this series" block from the summary — the formatting wasn't great and it cluttered the closing section.

---

Generated by Claude Code

[github-actions]

Notebook Changes

This PR modifies the following notebooks:

📓 managed_agents/CMA_remember_user_preferences.ipynb

View diff

nbdiff managed_agents/CMA_remember_user_preferences.ipynb (33424c3eb476cd56379435be086ccc228af1050d) managed_agents/CMA_remember_user_preferences.ipynb (30366fddbe85ed98737357d685ee76db7f69ec61)
--- managed_agents/CMA_remember_user_preferences.ipynb (33424c3eb476cd56379435be086ccc228af1050d)  (no timestamp)
+++ managed_agents/CMA_remember_user_preferences.ipynb (30366fddbe85ed98737357d685ee76db7f69ec61)  (no timestamp)
## modified /cells/0/source:
@@ -2,7 +2,7 @@
 
 Most agents start every conversation from scratch. A customer tells your shopping assistant their size, their budget, and which materials they avoid, and the next time they return, the agent has forgotten everything. They have to repeat themselves, and the experience feels generic rather than personal.
 
-We just introduced Memory in Claude Managed Agents to solve this. Think of it as a shared notebook your agent gets for each customer: Claude jots relevant things down during a session, and those notes are still there the next time the same customer comes back. Setup is a simple API call away.
+We just introduced [Memory](https://platform.claude.com/docs/en/managed-agents/memory) in Claude Managed Agents to solve this. Think of it as a shared notebook your agent gets for each customer: Claude jots relevant things down during a session, and those notes are still there the next time the same customer comes back. Setup is a simple API call away.
 
 In this guide you will build an example shopping assistant for a retail brand. The agent will learn a customer's preferences during their first visit, save them to a user-specific memory store, and recall them automatically on the next visit without being told again.
 

## modified /cells/25/source:
@@ -9,13 +9,8 @@ You built a shopping agent that remembers its customers across visits by:
 
 From here you can map your own user IDs to memory store IDs, seed stores from your existing customer data, and layer shared read-only stores on top for brand-wide knowledge.
 
-### Other notebooks in this series
-
-- [`CMA_iterate_fix_failing_tests.ipynb`](CMA_iterate_fix_failing_tests.ipynb) — the entry-point notebook. Introduces agents, environments, sessions, file mounts, and the streaming event loop through a do-observe-fix loop on a failing test suite.
-- [`CMA_operate_in_production.ipynb`](CMA_operate_in_production.ipynb) — production setup story: vault-backed MCP credentials, the `session.status_idled` webhook for HITL without long-lived connections, and the resource lifecycle CRUD verbs.
-
 ### Learn more
 
 - [Claude Managed Agents overview](https://docs.anthropic.com/en/docs/managed-agents/overview)
-- [Memory stores API reference](https://docs.anthropic.com/en/docs/managed-agents/memory)
+- [Memory stores API reference](https://platform.claude.com/docs/en/managed-agents/memory)
 - [Session resources](https://docs.anthropic.com/en/docs/managed-agents/memory#attach-a-memory-store-to-a-session)

---

Generated by nbdime

[github-actions]

Full Github Actions output

[github-actions]

PR Review

Recommendation: REQUEST_CHANGES

Summary

Small documentation polish on CMA_remember_user_preferences.ipynb: adds an inline hyperlink on "Memory" in the intro, updates the Learn More link to platform.claude.com, and removes the "Other notebooks in this series" block. The intent is good, but the link migration is incomplete, leaving the notebook with three different base URLs for the same Memory docs page.

Actionable Feedback (2 items)

• CMA_remember_user_preferences.ipynb (in cell with client.beta.memory_stores.memory_versions.list(...), line 575) — The inline link [Memory API reference](https://docs.anthropic.com/en/docs/managed-agents/memory) was not updated. After this PR the same page is referenced via both docs.anthropic.com and platform.claude.com within the same file. Update this link to https://platform.claude.com/docs/en/managed-agents/memory to match the other two Memory links.
• CMA_remember_user_preferences.ipynb (in "Learn more" section, line 625) — The anchor link [Session resources](https://docs.anthropic.com/en/docs/managed-agents/memory#attach-a-memory-store-to-a-session) still uses docs.anthropic.com. Consider updating the base to platform.claude.com for consistency (i.e. https://platform.claude.com/docs/en/managed-agents/memory#attach-a-memory-store-to-a-session).

Detailed Review

Link consistency

After this PR there are four references to Memory docs in the file, split across two different base URLs:

Line	URL
12 (intro, added)	platform.claude.com/docs/en/managed-agents/memory
575 (inline in Audit cell, unchanged)	docs.anthropic.com/en/docs/managed-agents/memory
624 (Learn More, updated)	platform.claude.com/docs/en/managed-agents/memory
625 (Learn More anchor, unchanged)	docs.anthropic.com/en/docs/managed-agents/memory#...

A partial migration is worse than either consistent state. The fix is to update lines 575 and 625 to use platform.claude.com as well.

Removal of "Other notebooks in this series"

Neither of the two removed cross-links (to CMA_iterate_fix_failing_tests.ipynb and CMA_operate_in_production.ipynb) linked back to this notebook, so removing them does not strand any reader arriving via a back-link. The removal is defensible and simplifies the conclusion section.

Intro hyperlink

Adding [Memory](https://platform.claude.com/docs/en/managed-agents/memory) in the intro is a useful improvement — it gives readers an immediate path to the reference docs without scrolling to Learn More.

Positive Notes

• The core notebook content, code, and explanations are untouched and remain high quality.
• The rationale for the changes is clearly articulated in the PR description.