Designing per-customer agent instances with isolated memory in AgentScope #1393
nottydadie
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I’m working on a multi-agent system using AgentScope and wanted to get some guidance on architecture and best practices.
My use case requires:
Running agents per customer (tenant)
Each agent instance should maintain separate memory per customer
Additionally, each agent (within a customer context) should have its own isolated memory (not shared across agents or customers)
So effectively:
Customer A → Agent X (memory A-X), Agent Y (memory A-Y)
Customer B → Agent X (memory B-X), Agent Y (memory B-Y)
I’m trying to understand:
What’s the recommended way in AgentScope to scope or namespace memory like this?
Should I instantiate separate agent objects per customer, or is there a built-in way to parameterize memory/context?
How should memory persistence be handled (e.g., external store, vector DB, session-based memory)?
Are there any patterns for scaling this when the number of customers grows?
How would this interact with an orchestrator agent delegating tasks to sub-agents?
Should I give separate run_id per run per customer?
OR
Just provide separate memory for each customer.
If anyone has implemented something similar or can point me to best practices/examples, I’d really appreciate it.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions