Memory stores are now labelled personal or project, and listing them runs immediately.
What's wrong with this entry?
The wording across memory tools no longer assumes stores are connected to an organization. Listing with no arguments now describes the memory stores available in this session, each store is reported as personal or project, and the credential refusal explains that project stores are shared with every collaborator. The listing tool also runs immediately rather than being deferred.
- Calling the listing tool with no arguments lists the memory stores available in this session, replacing wording about connected stores.
- The example path in the listing tool description now starts with
/feedback/. - Each listed store reports whether it is personal or project, and that value appears both in the tool output and in the per-call telemetry for the listing tool.
- The listing tool is no longer deferred, so it executes immediately when called.
- Attempting to write credentials into memory now returns: Memory stores are never a place for credentials, and project stores are shared with every collaborator. Remove the sensitive content and try again. This replaces wording that referred to the organization's connected projects.
- The save-memory tool description drops the word "connected", and the guidance line about credentials now covers every store rather than shared ones only.
- The listing prompt text is unconditional, but the listing tool itself remains behind the existing memory-store enablement check and is unavailable when that check fails.
list the memory stores and the documents in them, list the memory stores available in this session, Memory stores are never a place for credentials, and project stores are shared with every collaborator. Remove the sensitive content and try again.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.