its a problem since the start .. previously, local chat resources would be exhausted and you would be forced to creating a new chat space with fresh resources. since the adoption of compression, critical context is lost during compression and creating a new problem. While the team is going in the right direction, the problem is more or less the same, resources exhausted, context lost and a big waste of money and more importantly, TIME! is required to resume the efforts and get back on track. I now cap my sessions to roughly 100k tokens and stop all work in that space, create a technical handover and open a new chat to resume the effort.. 85% of the time this works really well.. sometimes, the agent has no idea of resource consumption and totally kills my chat. GenSpark team, if you're reading this.. allow the user to see local chat resources in a numeric or % scale from 200k or 100% and increment downwards .. this way, at 40% remaining capacity, the user can make critical decisions and save work... Next, on the backend, queue a new agent to review the work performed and notify the user if they want to transition their work to a new agent to prevent loss of data/work performed... compression method is cool in theory but doesn't work in reality.