The agent kept implementing the approach we already rejected because it never left the context window

When a developer redirects an agent away from an explored approach, the rejected branch often stays in the context window and keeps getting implemented. This piece explains why an agent remembers proposals without remembering their status, what extra abstractions and unrequested tests ship as a result, and how to keep an explicit active-constraint list separate from dropped exploration so a rejected idea stops steering the code.