memory changedmanaged-agents/memory
Nearest release: v2.1.308, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+3added
Lines−3removed
From line
370
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits20to this page, all time
The whole hunk
from line 370, old and new numbered
/
from line 370
370370
371371A maximum of **8 memory stores** is supported for each session. Attach multiple stores when different parts of memory have different owners or access rules. Common reasons:
372372
373* **Shared reference material:** one read-only store attached to many sessions (standards, conventions, domain knowledge), kept separate from each session's own read-write store.
374* **Mapping to your product's structure:** one store for each end user, team, or project, while sharing a single agent configuration.
375* **Different lifecycles:** a store that outlives any single session, or one you want to archive on its own schedule.
373* **Shared reference material:** one read-only store attached to many sessions (standards, conventions, domain knowledge), kept separate from each session's own read-write store
374* **Mapping to your product's structure:** one store for each end user, team, or project, while sharing a single agent configuration
375* **Different lifecycles:** a store that outlives any single session, or one you want to archive on its own schedule
376376
377377### How the agent accesses memory
378378
No line in this hunk matches that.