Persistent memory can carry useful context and stale assumptions. Decide what should survive a task before introducing it.
Define ownership
Separate user preferences from customer records and temporary working notes. Competent owners review retention and permitted reuse. Memory must not silently cross account boundaries.
Test changing facts
Correct a preference and revoke document access. Check later responses and tool calls. Outdated memory should not override authoritative business data.
Require a deletion path
Ask the partner for stored objects, access controls and removal behavior. A memory feature is maintainable only when operators can explain its scope and clear inappropriate state. Evaluate it against a version without persistence to confirm the added complexity serves the actual workflow.
Related reading : Scheduling agents across Europe: confirm timezone and current availability. Discuss your project scope with Sky Vaults.