Okay, so I've been testing Kimi for the last few weeks, mostly for brainstorming marketing copy and summarizing competitor reports. I really want to like itβthe analysis is often sharp.
But I keep running into a super frustrating bug: the chat interface will just reset on me mid-conversation. I'll be 10-15 messages deep into a thread, referencing previous points about customer journey mapping or A/B test ideas, and suddenly the entire sidebar refreshes. Poof. Context gone. I'm back to a brand new, empty chat window.
It doesn't seem to be tied to any specific action I'm taking. I've had it happen while:
* Pasting in a chunk of text for analysis
* Simply waiting for a response to generate
* Switching browser tabs for a minute and coming back
I'm on Chrome, latest version, and I've tried disabling my extensions. No luck.
Has anyone else hit this? I'm trying to see if it's a widespread platform issue or something on my end. It's a real workflow killer when you're building on a complex idea. For a tool that's all about long-context conversations, losing the conversation is a pretty critical flaw 😅
If you've found a fix or a workaround, please share! I'm curious if it's related to session timeouts, local storage, or something else entirely.
one stack at a time
Yes, I've seen this too. I use Kimi for project planning and it reset once when I was outlining remote team workflows. Have you noticed if it happens more often after a certain amount of time inactive? I lost a whole sprint retrospective template. It makes it hard to trust the tool for longer tasks.
That's exactly the behavior I've been tracking. I had a hunch it might be related to session timeouts or a memory leak in the frontend, but your note about it happening while actively pasting text or generating a response contradicts that. Those are active, in-focus actions that should keep a session alive.
It made me wonder if it's a specific interaction with Chrome's V8 engine. I've noticed my browser's memory usage for that tab spikes right before it resets, which makes me think it's hitting some unhandled allocation limit and the client just crashes and refreshes. It's frustrating because there's no error logged to the console you can catch.
Have you checked if it correlates with the *size* of the pasted text? I lost a long thread once after pasting a 2k-word document for summarization. Might be a trigger.
grep is my friend.