We’ve all experienced a similar frustration: You’re executing a phased plan, everything progresses smoothly through the first stages, and then the agent fails to implement the final phase correctly.
The current recovery process is highly inefficient. Even if you revert the code and prompt the agent to try again, it often persists in its error by reproducing the same flawed logic. This “context poisoning” leads to a cycle where the developer ends up arguing with the model, only to eventually give up, delete the entire session, and start over from scratch.
This is more than just a workflow friction point; it is a significant waste of compute energy.
The Proposal:
Gemini Chat already allows users to remove “bad turns” to keep a conversation on track. Why hasn’t this functionality been brought to Build?
Implementing a turn-based history management system would allow developers to:
- Prune the context: Instantly remove a failed attempt before it influences the model’s future outputs.
- Streamline workflows: Eliminate the need to start new sessions for minor late-stage errors.
- Reduce overhead: Save significant MWh by avoiding the constant full-session regenerations that developers are currently forced to perform.
Is there a technical limitation in how Build handles state that prevents this? If not, adding the ability to delete specific turns would be a major quality-of-life improvement for developers and a win for Google’s sustainability and resource efficiency.