I don't think cache shifting is a thing. But timing is. As far as I understand how it works, it you run a simple query on an already long sessions AFTER 5 minutes has transpired, then all of the cache...
Additionally, caching is not a complex thing we are implementing on our side anymore. It is handled by the providers who know what they are doing. So the chance that we are doing something wrong due to the caching is not really possible.
It's mostly likely how openclaw itself chooses how many files it wants to read any any given time.
Perhaps the solution is to remove the premium option so this doesn't happen to anyone. Maybe there is never a need for premium.
But overall maybe the best advice for users is to not keep the same session running forever. Was that waht you were doing? Keeping the same chat open without starting new ones?
It's mostly likely how openclaw itself chooses how many files it wants to read any any given time.
Perhaps the solution is to remove the premium option so this doesn't happen to anyone. Maybe there is never a need for premium.
But overall maybe the best advice for users is to not keep the same session running forever. Was that waht you were doing? Keeping the same chat open without starting new ones?
2
