Skip to main content

​
Introduction

Agent Memory is a powerful feature that allows you to personalize how an agent works specifically for you, without changing the core AOP that everyone else uses. This means multiple users can run the same agent with their own individual preferences, thresholds, and requirements automatically applied.

​
What is Agent Memory?

Memory is your personal context layer for any agent you have access to. When you add information to Memory, the agent will remember and apply those preferences every time you run it—but only for your runs. Other users running the same agent will have their own Memory settings applied to their sessions. Think of Memory as your agent’s personalized notepad about your specific preferences, while the main AOP remains the shared “company policy” that applies to everyone.

​
How Memory Works

When you run an agent, Duvo combines:
  • The agent’s core AOP (shared by all users)
  • Your personal Memory settings (specific to you)
  • Any run-time prompts you provide during that specific session
This allows the same agent to adapt to different users’ needs automatically, without requiring separate agents for each person or constant manual adjustments.

​
Why Use Memory?

Personal thresholds and preferences: Set approval limits, priorities, or preferences that match your role and authority level Saves time: Avoid providing the same context or guidance every time you run an agent Maintains consistency: Your preferences are automatically applied to every run, ensuring the agent always works the way you need it to Preserves shared workflows: The core AOP stays intact for everyone else while you get personalized behavior

​
How to Add Memory

To add information to Memory for a specific agent:

Open the agent

Open the agent you want to personalize.

Navigate to the Memory section

Navigate to the Memory section in the agent settings.
Agent Memory

Describe your preferences

Describe your preferences in plain English, just like you would in the Agent Builder.
Your preferences will now automatically apply every time you run this agent.

​
Deleting Memory Files in Bulk

When you have edit rights on an Agent or Queue’s Memory, you can clear out several files at once instead of removing them one by one.

Open the Memory section

Open the Memory section for the Agent or Queue.

Select the files to remove

Tick individual files, tick a folder to include everything inside it, or use Select all. Shift-click the first and last file in a range to select everything in between.

Delete and confirm

Choose Delete and confirm. Duvo removes the selected files together and updates progress as each one completes.
If some files can’t be deleted, Duvo removes the rest and shows how many were deleted; anything that failed stays in the list so you can retry it.

​
Real-World Examples

​
Example 1: Purchase Order Approvals

Your company has a PO approval agent that processes purchase orders. The core AOP requires human approval for orders over a certain amount. User A (Department Manager) adds to Memory: “Auto-approve all purchase orders under 5,000fromapprovedvendors.Flaganythingover5,000 from approved vendors. Flag anything over 5,000 for my review.” User B (Director) adds to Memory: “Auto-approve all purchase orders under 10,000.Forordersbetween10,000. For orders between 10,000-25,000,checkifthey′rebudgetedbeforerequestingapproval.Anythingover25,000, check if they're budgeted before requesting approval. Anything over 25,000 requires VP sign-off.” Both users run the same agent, but it automatically adapts to their different approval authority levels.

​
Example 2: Customer Communications

Your team uses an agent that drafts customer response emails. Different team members have different communication styles and preferences. User A (Account Manager) adds to Memory: “Always use a warm, conversational tone. Include my direct phone number in the signature. CC me on all customer correspondence.” User B (Technical Support) adds to Memory: “Keep responses concise and technical. Include links to our documentation. Don’t CC me unless it’s urgent.” The same agent produces emails that match each user’s style and preferences automatically.

​
Example 3: Report Generation

A weekly sales report agent pulls data and distributes reports to leadership. User A (Sales Manager - West Region) adds to Memory: “Only include data for California, Oregon, and Washington territories. Highlight accounts over $50K in annual value. Send the report to my regional team.” User B (Sales Manager - East Region) adds to Memory: “Only include data for New York, New Jersey, and Pennsylvania territories. Highlight accounts over $100K in annual value. Send the report to my regional team and VP of Sales.” Each manager gets a personalized report from the same agent without duplicating the workflow.

​
What to Include in Memory

Memory works best when you provide:
  • Personal thresholds: Dollar amounts, quantity limits, time frames specific to your role
  • Preferences: Communication style, formatting choices, notification preferences
  • Contextual rules: Exceptions or special handling for your department, region, or responsibilities
  • Contact information: Who should be notified, CC’d, or involved in your runs
  • Priority guidance: What matters most to you when the agent needs to make judgment calls

​
What Happens When an Agent Moves to Another Team

When an Agent moves to another team, its Memory moves with it, along with the Memory attached to any Queue that moves in the same operation. The Agent arrives on the new team with its context intact, so runs behave the same way after the move as before it.
If the destination team already has Memory for that Agent or Queue — which happens when the Agent lived on that team before and left its Memory behind — the destination team’s existing Memory is kept and the incoming Memory stays where it is. Nothing the destination team already relies on is overwritten.
Archived Memory on the destination stops the move, and the error identifies the Agent or Queue that is blocking it. Restore or delete that Memory on the destination team, then move the Agent again. Duvo stops rather than silently leaving the Agent’s Memory behind.
Unusually large Memory is also refused rather than moved in part. The message names the limit — clear out Memory the Agent no longer needs, then retry.

​
Key Takeaways

  • Memory personalizes agent behavior for your specific needs without changing the core AOP
  • Multiple users can run the same agent with their own individual Memory settings
  • Memory is perfect for thresholds, preferences, and personal context that applies to all your runs
  • Memory complements (but doesn’t replace) run-time prompts for one-time guidance
  • You can update Memory settings at any time
Agent Memory ensures that automation works the way you need it to, while maintaining consistency and collaboration across your team. Set it once, and let your agents remember what matters most to you!