Summary
Pi remembers durable, short facts and preferences across your Sessions
Memory has four levels: just you, your team, everyone with your role, and your whole organization
Memories are created conversationally. Ask Pi to remember something, or let it save a preference it infers from how you correct it
Who is this article for?
Planhat users on Planhat OS
Anyone else who would like to learn about Memory
Article contents
What is Memory in Planhat OS?
A "memory" is a short, durable fact that Pi keeps across sessions: a preference or a standing rule. Every time you send a Session message, Pi always assembles the memories that apply to you and reads them before answering.
Note on Memory and Skills
Memory holds facts. Skills hold procedures. "My competitors" is a memory; "here's how I run a renewal review, step by step" is a Skill. They work together: a Skill describes the process, Memory shapes additional context as to how it's carried out for you.
Memories are background context, not instructions. Pi treats them as internal notes. Memory can't grant access or permissions to data you couldn't otherwise see, and can't override how Pi is configured to behave.
The four levels of Memory
Every memory belongs to one level:
Level | Applies to | Typical use cases |
Personal | Just you | How you like answers presented; your own coverage arrangements |
Team | Everyone in that Team | A convention the team follows; who covers what during a holiday period |
Role | Everyone holding that Role | Guidance for everyone with the same permission profile, e.g. all Support agents |
Organization | Everyone in your tenant | A company-wide rule, definition, or naming convention |
What Pi reads for you is the combination: every organization-wide memory, memories for each Team you're in, memories for each Role you hold, and your own personal ones.
đ Tip
Pi defaults to the narrowest level that fits. A preference you express defaults to become personal memory unless it clearly applies to a whole group.
Why use Memory?
Cross-session knowledge. Each session contains only its own context. Memory carries over important facts across Sessions.
It scales decision-making An organization-wide memory means every colleague benefits from the same definition - for example, custom nomenclature, which metrics are valuable. This consistency is otherwise hard to achieve in a distributed organization.
How to add a memory
There are two routes:
Ask directly. Tell Pi to remember something: "remember that I want summaries to lead with ARR", or "from now on, always include churned accounts in portfolio counts." Phrasing it as a standing rule â "always", "from now on", "remember this" â is what makes it a confirmed memory rather than an inferred one.
Let Pi infer it. When you correct or redirect Pi, Pi treats that as a likely durable preference and saves it as unconfirmed. You don't have to ask explicitly for it to be saved.
Confirmed memories are created when stated as a standing fact, or affirmed when asked. For example: "AlwaysâŚ", "from now onâŚ", "remember thisâŚ", or agreeing with a memory Pi read back to you
Unconfirmed memories are Pi's own inference from how you behaved. For example, a simple redirect, like "show ARR instead" implies a preference without stating one
How to review what Pi remembers
Ask. "What do you remember about me?" returns everything that applies to you.
You can also ask for a subset: "What do you remember about how I like reports formatted?", or "What does Pi remember for my whole organization?"
As of now, there's no separate page to manage Memory. Review Memory by asking in chat.
How to correct or remove a memory
To correct one, just say the new version: "Actually, lead with seat count, not ARR." Pi replaces the old memory rather than adding a second, contradicting one.
To remove one, say "forget that", or name what should be dropped: "forget that I'm covering Hulk's accounts."
To go back to default behaviour, ask: "just use my profile name", "go back to normal." Pi deletes the memory that overrode the default rather than saving a new memory describing the default.
đ Tip
If you notice Pi acting on something out of date, correcting it is a better resolution to an improved response. Rather than stacking more memories, fix the existing one, so contracting memories donât build up.
Who can save memories at each level
Level | Who can save |
Personal | You, for yourself only. Nobody can write to another User's personal memory, not even an Admin |
Team | Managers of that Team, and Admins |
Role | Users of that role only |
Organization | Admins only |
If you ask for something to be remembered organization-wide and you don't have the rights, Pi will tell you and offer to save it as a personal memory instead.
đ Note
Personal memory is genuinely personal. There is no route, including for Admins, to write a memory into another User's personal scope.
Limits and expiry
Each memory is up to 500 characters. One fact per memory.
Memories can optionally carry an expiry date, set when you state one: "until the end of August". They're removed automatically when it passes
Memories without an expiry are kept until removed
There's a limit on how much memory is read per message. If a lot has accumulated, Pi prioritises your personal memories, then organization-wide, team, and role
đ Tip
Because your personal memories are read first, personal corrections always take effect. Broad memories are the ones at risk of being crowded out â which is a reason to keep organization-wide memory to genuinely universal facts.
Frequently asked questions
How do I see what Pi remembers about me? Ask Pi in chat directly what it remembers about you.
Can I set a memory that expires? Yes, youâll need to state the expiration date, otherwise there is none.
How long can a Memory be? Up to 500 characters.