Blog·Learning

How Perplexity memory works: what it remembers and how to delete it

By Shardul Mane·6 min read

A blurred, grainy photo of a sunlit tree against a blue sky, with the supermemory logo and the headline Understanding Perplexity memory.

Yes, Perplexity remembers you between conversations. Its Memory feature draws on saved memories (preferences, interests and details you share) and your past searches. You can turn either one off in Settings, under Memory, delete saved memories there, and delete past searches from your History. Max subscribers using Perplexity Computer also get Brain, a separate memory with its own controls.

Everything below is checked against Perplexity's help center on October 16, 2026. Perplexity changes these settings often, so the linked pages are the source of truth.

Does Perplexity remember previous conversations?

Yes, in two ways (Perplexity Help Center):

  • Memories: the preferences, interests and information you share. Perplexity stores key details as you ask questions, building a memory bank you can manage in Settings.
  • Search history: your past questions and answers, used when they make a new answer more relevant.

Perplexity decides when to use them based on the question, and when a memory shapes an answer, it shows up among the answer's sources. Memory works across all of Perplexity's models and search modes (Perplexity changelog, Dec 2025), so switching models inside Perplexity doesn't reset it.

It does stay inside Perplexity. Perplexity doesn't import chat history from ChatGPT or Claude (Perplexity Help Center), and what it remembers is managed in Perplexity's own settings.

What is thread continuity in Perplexity?

Thread continuity means a conversation keeps the context of your earlier questions, so follow-ups build on previous answers without you repeating the background. Perplexity now calls threads sessions. A session holds your first question, every follow-up, every answer and the sources used, and it's designed to keep context for follow-up questions. If you switch topics often within one session, it may need some guidance to stay on track (what is a session, session capabilities).

Continuity within a session and Memory across sessions are different features. A session remembers one conversation; Memory carries details from one conversation into the next.

What is Perplexity Brain?

Brain is a separate, self-improving memory for Perplexity Computer. It builds a working model of your projects, people and files from your sessions, connected tools, the files you create in Computer and your corrections, and it runs in the background (what is Brain). Each entry links back to its source, and the entries are organized into Concepts, Entities and Workstreams that you can browse and edit.

As of October 2026, Brain is rolling out in research preview to Max and Enterprise Max subscribers using Computer. Search doesn't access Brain, and Brain ignores incognito sessions. Perplexity's own summary: Memory helps Computer know you, and Brain gives Computer the working context to move your work forward.

Where are Perplexity's memory settings?

Go to Settings → Memory (Perplexity Help Center). You'll see:

  • Use search history: a toggle for referencing past searches.
  • Notes: a toggle for saving simple details from your sessions for future answers.
  • Manage memories: your full memory bank, where you can search, filter and delete entries.
  • Brain (Max subscribers): a toggle for building structured memories.

If you remember Memory living somewhere else, it moved: the sidebar item that was called Customize is now Plugins, and Memory has moved to Settings. Plugins is rolling out gradually, so some accounts still show Customize for now (Perplexity Help Center).

How to delete Perplexity memory

To delete one memory or all of them:

  1. Open Settings → Memory.
  2. Click Manage memories to open your memory bank. Search or filter for the entry you want.
  3. Click the trash icon next to a memory to delete it, or use clear all to delete every memory at once.

A deleted memory leaves the memory bank and isn't used in future answers. Perplexity may keep a log of cleared memories for up to 30 days for safety, debugging and to make sure memories aren't recreated right after deletion (Perplexity Help Center).

To stop a past conversation from shaping future answers, delete that session from your history. Open History from the sidebar; you can delete individual sessions or all of them (what is a session).

To stop Perplexity from using memory going forward, turn off Notes and Use search history in Settings → Memory. Each toggle works on its own. Turning Memory off doesn't clear existing memories, so delete them in Manage memories as well.

To edit or delete what Brain has learned, open the Memory page in Computer, where every entry can be edited or deleted. To stop Brain from writing new knowledge, turn it off under Settings → Memory settings → Brain (what is Brain).

For a one-off private question, use incognito. Memory and previous searches are always off in incognito, and questions asked there are never retained or used in memory.

What does Perplexity memory keep, and what doesn't it?

Perplexity says it has taken steps to reduce how much sensitive information, like health or financial details, memory retains. It also says memory is generated by a model that favors how often you ask about something and what you share, so check your memory bank if you've discussed sensitive topics (Perplexity Help Center).

On consumer accounts, Perplexity may use content from memory to improve its models. Its Memory article says you can turn that off with AI Data Retention in Settings → Preferences → Artificial Intelligence, though its Brain and Enterprise articles describe that setting as covering searches only.

How is Enterprise memory different?

Enterprise memory works the same way for each user, with differences in control and ownership (Memory for Enterprise organizations):

  • Admins control Reference search library (Use search history) and Reference saved memories (Notes) for the whole organization. If an admin turns one off, it's off for everyone.
  • Memories created in an Enterprise organization belong to the organization. A user who leaves loses access to them.
  • When admins disable Memory for the organization, existing memories are deleted, and the same applies when a member disables it for their own account.
  • Perplexity never uses memory content to train models for Enterprise users.

Projects add another layer. In Computer, a project can have a shared Brain that everyone in the project sees, and the project owner decides whether sessions also draw on the personal memory of whoever started them. The help center's two articles describe the project controls slightly differently, so check the one that matches your account type.

Check what Perplexity remembers with a test

Use a harmless, made-up detail, like a demo project's code name. Note where you shared it, whether it shows up in Manage memories, and what a fresh conversation cites when you ask about it.

Then change the detail and ask a related question. If the old answer persists, check whether it comes from a saved memory, a past session or text already in the new conversation. Each route needs a different fix: delete the memory, delete the session, or start a new one.

Building memory like this into your own app

Perplexity's memory is a product feature, so it only works inside Perplexity. If you're building an assistant and want the same behavior, the design questions carry over: can users inspect what's remembered, see where it came from, correct it and delete it, and predict when it will be used?

A memory API gives you those parts without building them from scratch. With supermemory, each user gets a namespace, their profile comes back with one call, and most profile entries carry a memory ID you can forget (profile API). The user-preference guide walks through it with code, the long-term memory guide covers the design, and the MCP context-sharing guide shows how to share one memory across assistants like Claude and ChatGPT through our MCP server.

  1. How AI memory actually works. A beginner's guideHow AI apps remember things between chats, why a bigger context window doesn't solve it, and the parts every memory system shares.
  2. We're open sourcing the company brain. Here's how we designed the multiplayer harnessCompany Brain is now open source. A walkthrough of the multiplayer harness behind its Slack experience, from proactivity and memory boundaries to approvals and recovery.
  3. Jev changes a lot in memory & context engineering. Here's exactly how.We tested Jev across reranking, chunking, observation, and harness decisions. Here is where fast decision models help memory systems, where they cost more, and where they still fall short.
  4. I reverse-engineered Instinct's memory. Here's exactly how it worksInstinct keeps its memory as git-tracked markdown files, found with grep rather than vectors. Here is the whole system as far as black-box probing can reconstruct it, and how to rebuild it on supermemory in about 60 lines.
  5. An update to supermemoryWe've discontinued the supermemory company brain and Nova. Everyone who was charged has been refunded, our MCP and plugins continue to run, and we're going all in on the memory engine.
  6. Scaling Conversations: How Adapta Grew Usage Without Losing ContextAdapta added Supermemory as a persistent memory layer so every conversation keeps its context — letting the team scale usage without losing the thread.
  7. How Chatarmin Ditched RAG and Went Memory-Only with SupermemoryChatarmin replaced a heavy RAG pipeline with Supermemory's memory layer — cutting average AI response time from 40s to 12s and token usage by 40–50%.
  8. SMFS: making agentic retrieval 55% cheaper AND more accurateWe launched SMFS.ai (Supermemory Filesystem) a few weeks ago, with a simple bet: We can redesign the filesystem specifically for agents, with special files, structures, and commands that it can use for it's tasks. Today, SMFS is used by hundreds of companies to power their agents.
  9. Introducing Dynamic Dreaming: supermemory now connects the dots, for you.Dreaming is magical. TLDR: We're launching Dynamic Dreaming in supermemory today, which automatically works if you're using supermemory in any way - API, OpenClaw, Hermes agent, etc.
  10. Dear reader, we just made supermemory insanely cheap... the Context CloudWhen I first started building supermemory, I had one goal: To build the best memory system for AI. I would talk to customers, and find out that memory was not the only thing they needed - They were all setting up 7-8 different vendors at the same time.
  11. Introducing @supermemory/tools v2.0.0Today we're releasing v2.0.0. This release unifies the API across all agents sdk integrations from AI SDK to Mastra, makes conversation identity a first-class concept, and ships with memory saving on by default.
  12. Solving the Precision-Recall Tradeoff: Search Result AggregationWhen you're building memory for AI, search is your foundational layer. The way search generally works is straightforward: the user defines a query, and then sets a limit (top-K) on how many search results they want returned. Usually, this is set to 10 or 20.
  13. OpenClaw Memory Problems: Why It Forgets and How to Fix It (2026)OpenClaw remembers by writing Markdown files in its workspace, so it forgets anything the agent didn't save. Why that breaks down, how the supermemory plugin recalls and saves on every turn instead, and how to install it, free on every plan.
  14. Stateful Coding Agents with Memory: Build Long-Running Agents (2026)We built a plugin for Claude Code and OpenCode that gives your coding agent persistent memory. It remembers your preferences, learns your codebase, and never loses context mid-conversation. The result is an agent you can run for months without starting over.
  15. Clawd / Molt bot's memory SUCKS. We gave it supermemory.I'm the founder of supermemory. Clawd/Molt bot is blowing up right now, with many, many use cases. I set it up, too, and have been using it through telegram. TLDR: just go to https://supermemory.ai/docs/integrations/clawdbot to set up supermemory for your clawd bot.
  16. Catch up with our UNFORGETTABLE Launch WeekOver the last year, one belief has guided almost everything we’ve built at Supermemory AI becomes meaningfully useful only when it remembers. Memory shouldn’t be something developers rebuild from scratch. It shouldn’t be fragile, expensive, or trapped inside a single tool.
  17. Empowering the Next Generation of Founders: Supermemory Startup ProgramIf there’s one thing we’ve learned while building Supermemory, it’s that most startups don’t fail because they didn't build features; they fail when infrastructure slows them down, or they built too slow.
  18. Building code-chunk: AST Aware Code ChunkingAt Supermemory, we're building context engineering infrastructure for AI. A huge part of that is dealing with code: ingesting repos, understanding structure, and making it searchable. The problem is that most code chunking solutions are terrible. We built code-chunk to fix this.
  19. Supermemory raises $3 million with the best memory engine for LLMsToday, I am excited to announce our first funding round to accelerate our mission of building an interoperable, scalable and reliable memory for LLMs and agents. Memory is one of the hardest challenges in AI right now.
  20. Mem0 vs Supermemory: Why Scira SwitchedScira AI moved its production memory layer from Mem0 to Supermemory. This is what failed, what improved, and how the team evaluated the two systems.
  21. Never Record Again: How Montra Uses Supermemory to Rethink Video CreationCampbell Baron, the founder of Montra, has been making videos since he was twelve. By thirteen, he was already doing brand work. Today, he’s betting on a very different future for creators: a world where recording is the exception, and most videos are generated from scratch.
  22. Unified Memory That Works Where You Work: Your Second Brain With SupermemoryHi everyone, I’m Dhravya, the founder of Supermemory. I want to start with a little story behind why this product means so much to me. You can also skip straight to what it is and how it works below.
  23. Supermemory just got faster on PlanetScaleWhat is Supermemory? Supermemory completes the missing part of the LLM puzzle: memory. Just as memory is crucial for human intelligence, it's essential for truly intelligent AI systems.
  24. Faster, smarter, reliable infinite chat: Supermemory IS context engineering.People are obsessed with prompts and prompt engineering. Sure, what you say is important, but what the model knows when you say it is the difference between a stateless text generator and an intelligent AI system. In short, context is the most crucial component.
  25. We solved AI API interoperabilityOne API to rule them all, One spec to find them, One library to bring them all and in the TypeScript, bind them. When we were building the Infinite Chat API, initially, we only supported the OpenAI format. This was fine, until a lot of our customers started asking for more.
  26. The Wow Factor of Memory - How Flow Used Supermemory To Build Smarter, Stickier ProductsOverview: Flow is a note-taking app built around a bold vision: to create a more personal, context-aware writing experience powered by AI. At the heart of this mission is memory.
  27. The UX and technicalities of awesome MCPsLast month, we launched the Supermemory MCP, mostly to test our own infrastructure and get some initial traction. It blew up. To my absolute surprise, the initial launch itself got half a million impressions (!!!). Then, we launched and got #2 on ProductHunt too.
  28. Architecting a memory engine inspired by the human brainLanguage is at the heart of intelligence, but what truly powers meaningful interaction is memory — the ability to accumulate, recall, and contextualize information over time. Large Language Models (LLMs) have mastered language, but memory remains their Achilles’ heel.
YOUR PRIVACY

Change or withdraw any time via Cookie settings in the footer. Read our cookie notice.