Back to ideas
Agentic AIPractice reflection2 min read

Why my two agents keep separate memory

Frequent briefings and business analysis need different context, with separate decisions about access to key records.

My work agent retrieves references, analyzes questions, and drafts material. My personal agent handles more market information, news, and daily briefings. Their information has different frequency and purpose, so I keep their memory separate.

Otherwise a day of fragments can crowd the context needed for a longer task.

Shared resources, separate write decisions

Both can use shared references and tools. The personal agent has read-only access to key records, with changes passing through the designated work process.

Separate memory addresses context. Write access also needs tool-level restrictions; a role description alone does not enforce it.

How I choose the boundary

I ask who a mistaken write affects, whether it can be recovered, and what checks a change requires. A personal briefing and a record used for business conclusions can have different rules.

New tools or tasks require another look at these boundaries. The number of agents matters less than whether their responsibilities and permissions fit the work.