De-cluttering agent graphs: Moving state out of framework memory

Analyzing state payloads in complex multi-agent pipelines usually reveals a major bottleneck: roughly 70% of memory graphs are spent tracking transport state, verifying tool execution, passing user IDs, and stitching multi-day conversations across restarts.

We are essentially rebuilding message queues inside framework contexts.

The Refactor:

• Strip out heavy state graphs for asynchronous, long-running workflows.

• Provision an isolated email endpoint per sub-agent (using agentmail.to for routing).

• Let standard email threads act as the persistent state memory.

Benefits:

• Token Efficiency: Context is queried on-demand rather than passed in every state payload.

• Inspectability: Execution steps are natively human-auditable.

• Resilience: State persists across script restarts automatically.