Follow-ups stay in the same thread

Until recently, a page reload meant you lost the context of your conversation with the Mu agent. You’d have to restate your question or re-enter details. That friction is gone now. Follow-up questions stay attached to the same thread, even after a reload. You can ask a question, get an answer, step away, come back, and pick up where you left off without copying or re-typing.

The change is modest by design. No new bells or whistles. The agent simply remembers the conversation history across a page load. If you ask for today’s weather, then reload to check your email, then ask “what about tomorrow?” the thread keeps the context. It works because the conversation state is stored locally in the browser session, not on a server tracking you. No account required, no extra data collected.

This makes the agent feel more like a real conversation than a series of isolated queries. You can clarify, narrow, or pivot without repeating yourself. It’s the sort of baseline behaviour that should have been there from the start. Now it is. And if you self-host the binary, the same improvement applies — the thread persists across reloads there too, because the state lives in the frontend, not on our end.