Your Coding Agent Keeps Rebuilding the Project
Coding agents are getting very good at doing work. The part that still looks wrong to me is what happens between the steps: the system keeps rebuilding project state that already exists.
A planner creates a plan. A coding worker changes the repository. A tester finds a regression. A reviewer makes a decision. Then the next worker starts — and much of the same project context is assembled again: plans, progress files, diffs, logs, test output, and previous decisions.
The problem is not that the model forgot one fact. The problem is architectural: the working state of the project is still too often attached to the agent session.
The Project Should Be the Persistent Object
This is the assumption behind Tenrec. Instead of trying to keep one agent, one conversation, or one context window alive, Tenrec keeps the operational state of the project outside the worker: goals, tasks, accepted decisions,...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
