Memory-Augmented Agent Pattern
Persistent memory lets an agent remember user context and preferences across sessions, instead of starting fresh every conversation.
Why This Pattern
The trade-off is convenience versus governance debt. Every piece of stored context is something you now have to justify retaining, secure, and eventually delete — so the reasoning discipline is to store only what changes the next conversation's behavior, not everything the user has ever said. That's why Workato's actual scope for this is deliberately narrow: user context and preferences, not a general memory model.
When to Use It
- Users move between conversation threads or MCP clients and shouldn't have to re-establish context each time.
- The genie needs to recall location, organization, language, or data-presentation preferences without re-asking.
When NOT to Use It
- The information belongs to a single business object and needs reporting over time — that's Persistent State & Data Enrichment.
- You haven't defined a retention policy — don't persist user context indefinitely without one, even for internal deployments.
How It Works in Workato
- Tools to store and retrieve user context.
- Persistent storage: Workato Files, Data Tables, or Lookup Tables.
- Explicit instruction in the genie or MCP client prompt to use the stored memory.
Source: MCP Cookbook V1.0, p. 25