3 ms·

yeah, starting a new conversation and asking it to review the logs of the old one for context is my current workaround. still its a weird bug