Chat remembers.
Morrison Chat now carries durable facts across conversations: a working note for the session, your own preferences, and facts about the site shared with the team. Curated, not recorded, and never a substitute for live data. Automations share it too.
Every chat used to start from zero. You would explain again that reports go to the CMO, that the brand never says “solutions”, that the Nordic markets matter more than DACH. Chat now remembers - about you, and about the site - so each conversation starts where the last one left off.
Three kinds of memory
- A working note for this chat. A short scratchpad the agent keeps current as a long session moves - what you are working on, what has been decided, what is next. A conversation that runs for days never loses the thread.
- Your own preferences. Private to you and carried across every site you work on: how you like reports structured, the tone you want drafts in, the things you always want skipped.
- Facts about the site, shared with the team. Brand, audience, positioning, tone of voice. Tell the agent to remember something for the team - “remember for everyone: we never link to competitor pricing pages” - and every colleague working on that site benefits from it in their own chats.
Curated, not recorded
Memory is not a transcript. The agent saves the things that will still be true next month and leaves the rest. It prefers updating a fact to piling on a new one, and most turns write nothing at all. You can ask what it remembers, ask it to forget something, or correct a fact in plain language.
And memory never stands in for live data. Page content, rankings and metrics come fresh from your crawl and your integrations every time. If a memory ever disagrees with what the data says today, the data wins.
Memory and context
Memory sits alongside chat context, the standing guidance you write yourself in your settings. Context is what you tell the agent; memory is what it picks up along the way. Between them, the agent knows your site the way a colleague who has worked on it for a year does.
Automations remember too
Automations share the website memory, so a scheduled run knows the same brand facts your team does. And a run can look back at its own previous output when the task calls for it - so a weekly digest can tell you what changed since last week, not just what this week looked like.
Try it
Memory is on in every workspace, nothing to enable. Tell the agent one thing about how you like to work, start a new chat tomorrow, and notice that you did not have to say it again.
Tell us what it remembered that mattered at hello@morrison.app.
See how Morrison can help
Crawl your site, chat with your content, and run AI-powered workflows at scale.
Browse use cases

