Memory
Ask Ysra or any colleague to remember facts and preferences across conversations, see each change on the answer, undo it, and edit or forget what it remembers.
On this page
Memory is the set of facts and preferences Ysra carries from one conversation to the next, so you don’t have to repeat them. Use it for lasting things about you and your work, such as when your fiscal year starts or how short you like answers. This page covers adding, scoping and forgetting memories, and where they are used; conventions for code changes belong in Rules & instructions.
What Ysra remembers#
Ysra and your colleagues save a memory when you ask them to, or when the conversation shows something lasting about you or your work: a preference, a correction, a changed requirement, or news such as a new role. Every memory is visible in Library → Memory, and you can edit or forget any of them. “Credentials and retrieved company content are never stored.”
When an answer changes your memory#
An answer that saved, updated or forgot a memory says so in one line at its top: Saved to memory, Memory updated, Forgot: …, or a count such as Memory updated · 3 changes. Select the line to see each change:
- what was saved, or for an update the old words (struck through) and the new ones;
- where it is used: Yours, in every workspace or This workspace only;
- Undo, which puts it back as it was;
- All memories, which opens Library → Memory at that memory.
When Ysra asks first#
Sometimes the answer doesn't save anything by itself. It asks instead: Save to memory?, Update memory? or Forget this?, with why it asks, Save (or Update, Forget) and Not now. Nothing is kept until you choose. Ysra asks first when:
- the words didn't clearly come from you;
- the answer or the conversation read something from outside, such as a web page, an email or a forwarded message (an edited or retried message counts the same as the first version);
- it is about your private life, such as getting married, a new baby or a move, unless you asked Ysra to remember it in that message.
Adding a memory#
Open Memory#
Go to Library → Memory.
Write it#
Type the fact or preference in your own words, for example Our fiscal year starts in April.
Choose its kind and scope#
Pick a kind (below) and choose All colleagues or one colleague.
Save it#
Choose Remember.
You can also ask in a conversation, to Ysra or any colleague: “Remember that releases go out on Thursdays.” It goes into your memory, and the answer says so at its top. In a team conversation, something about you goes to Ysra unless you address a colleague.
The four kinds#
| Kind | Use it for | Example |
|---|---|---|
| Preference | How you like answers. | Keep answers short and list assumptions. |
| About you | Your role and what you work on. | Leads the billing team; reviews every invoicing change. |
| Project context | Lasting facts about your work. | Billing 2.0 replaces the legacy invoicing service. |
| Standing instruction | Something Ysra should always do. | Always give dates in ISO format. |
Scope#
| Scope | Who uses the memory |
|---|---|
| All colleagues | Ysra and every colleague. |
| One colleague | Only that colleague. |
A memory is also used either in every workspace or in this workspace only. In an Enterprise workspace, what is learned there stays in that workspace: changing a memory you keep for every workspace makes a version for that workspace and leaves the original as it was.
A colleague with Own notes turned on also keeps notes of its own from your conversations. Those are only that colleague's. Your own memory, what you ask to remember, works for every colleague whether Own notes is on or off.
Where memory is used#
| Place | Uses memory |
|---|---|
| Ask | Yes, for Ysra and every colleague. |
| Code threads | Yes, Code threads read your memories too. |
| Shared colleagues | The memories of the person using it, never yours. |
| Public colleagues | None, and nothing from your own conversations. |
Within one conversation, Ysra also remembers the earlier turns, without saving them as memories.
Memory or Rules & instructions?#
| Memory | Rules & instructions | |
|---|---|---|
| What it is | Facts and preferences about you and your work. | Conventions for code changes. |
| Best for | Our fiscal year starts in April. | Use pnpm. |
| Used in | Ask and Code threads | Code threads |
| Where to manage it | Library → Memory | Rules & instructions |
What is never stored#
“Credentials and retrieved company content are never stored.” Memory is not a copy of your Slack, Jira, Gmail or file content.
See, edit or forget a memory#
Library → Memory lists everything stored. Each memory shows where it is used (every workspace, or only one), where it was learned (a link to the conversation, or “Added by you”) and its date.
- Edit changes its words or its kind.
- Forget removes it, and it no longer shapes answers.
To undo a change an answer just made, use Undo on the line at the top of that answer.
On the phone#
Open Settings, then “What Ysra remembers”. Add a memory with Remember something, or remove one with Forget.
If an answer ignores a memory#
| Why | What to do |
|---|---|
| Ysra asked Save to memory? and you didn't choose Save. | Save it from the answer, or add it in Library → Memory. |
| The memory is scoped to another colleague. | Change its scope to All colleagues, or ask that colleague. |
| It was forgotten. | Add it again. |
Related#
- How Ysra finds and uses your information — memory next to every other source.
- Colleagues — the Own notes capability.
- Rules & instructions — conventions for Code work.