Recommended
How Salesforce engineered persistent memory for Agentforce agents (opens in a new tab)
You will learn how the Agentforce team designed persistent memory to solve stateless agent limitations, including retrieval strategies, latency tradeoffs, and privacy controls.
Why read this
Readers will understand why memory was moved into the Reasoner and how to enable it using Agentscript.
The Salesforce Engineering team built Agentforce Memory to eliminate the stateless nature of enterprise AI agents. Without persistent memory, users must repeatedly provide context, which increases friction and slows task completion. The team standardized industry terminology around memory types before designing the architecture.
Early prototypes relied on recent conversation history, but the team shifted to semantic retrieval to capture older but relevant information. They evaluated multiple approaches and selected keyword search during pre-orchestration to keep the context window bounded and minimize latency. Moving memory directly into the Reasoner replaced manual action configurations, simplifying administration and improving developer ergonomics.
Privacy and user control were treated as core architectural requirements rather than afterthoughts. Administrators can enable memory globally, while individual users manage preferences through a console or conversational commands. Enabling the feature requires adding a context.memory block to Agentscript, allowing the platform to handle curation and injection automatically.
Read the original at Salesforce Engineering (opens in a new tab)