Agent Context Accumulation: More Harm Than Good
We discussed context mixing in a God Agent. I suggest using this term for the default situation where one agent has access to everything.
It works like this. One agent knows your context very well. It knows every decision made during the project’s development.
Including mistakes. These mistakes accumulate.
At some point, you decide to clean things up. You write a concept from scratch and formulate fresh ideas.
But you do this in the same God Agent, which knows your project well.
Now imagine that the agent has 100% of the context about how the project WORKED, and k (< 100%) of the context about how you want the project to work. At the same time, k will always be much less than 100%. It is impossible to get absolutely everything out of your head.
The result is that the agent will make a mishmash of the old architecture, with minor changes toward what you want.
Literally, only a couple of arrows will change in the same architecture diagram.
The solution I suggest is to start a new agent with a clean context. It will offer a fresh perspective without looking back at what has already been done.
You can then give it the old context and ask it to criticize it, not refine it. Otherwise, it will once again reduce everything to some shared solution.
This is more complex than doing everything in one God Agent, but it is managerial work that cannot be avoided, though it can be partially automated.