Agent memory architecture

Tue, 22 Sep 2026 00:00:00 +0000

Part of my AI Security Engineering series, a local email-to-calendar agent I build, then attack, then harden. If you have not set up the lab yet, start with Set up your lab. The lessons are on GitHub, and the agent itself lives at t0ul/emaildrop.

Shared memory between agents

The last three posts secured one agent’s memory of itself: a durable log it can verify, side effects that fire once, a summary that does not launder instructions. This one steps up to the architecture, because real systems are rarely one agent. They are several, cooperating, and they coordinate through shared state, a blackboard that each can read and write. The moment memory is shared, it inherits every multi-tenant problem a database has, plus one that is specific to agents.

Multi-Agent on t0ul

Agent memory architecture

Shared memory between agents