Memory
Memory holds what you or your team asked WeHarness to remember: preferences, decisions and facts that should carry over to later sessions. Examples are “we deploy with Docker Compose” or “answer in Turkish”. WeHarness uses them in later sessions and in plans, and says so when one shapes its answer.
Adding to memory
Section titled “Adding to memory”- In a session, say it in your own words, in any language: “remember that we never deploy on Fridays”. You can also type
/remember. Under the reply WeHarness shows what it kept, with Undo. - In Memory (in the sidebar), add an item yourself.
WeHarness remembers only what a person said. It never remembers text from your files, repositories or tool output, and it never writes memory on its own initiative.
Some items wait for you before WeHarness uses them:
- Learned while reading. You asked WeHarness to remember something after it read your files, repository or tool output. That content could have shaped the item, so it waits under the reply as Keep for later sessions?, with Keep and Discard. You also find it in Memory, under Waiting for you.
- Repeats an old item. It repeats something you stopped using.
Nothing uses a waiting item until you keep it. An item that holds a secret (a key or token) or an invisible character is refused, never stored.
Each item records who said it, when, and the session it came from.
| Scope | Who it applies to |
|---|---|
| This repository | Every session on the repository it was said in |
| Whole workspace | Every session in the workspace |
| Only you | Your own sessions; nobody else in the workspace sees it |
What memory is not
Section titled “What memory is not”A remembered item is a stated preference, not a verified fact. It never grants a permission and never stands in for an approval. When your latest message says something different, the latest message wins: WeHarness’s own rules and your newest message always rank above what it learned.
A reply always uses the memory it started with, even if you change an item while WeHarness works on it.
Plans treat remembered items as preferences. A requirement comes from your brief, not from memory alone.
Changing and deleting
Section titled “Changing and deleting”In Memory you can edit, stop using or delete any item you can see:
- Editing keeps a new version.
- Stop using keeps the item without using it. It moves to Not used, and you can use it again later.
- Deleting removes every version at once; use it when something must be erased. WeHarness stops using the item from your next message. Only a record that the item existed, without its content, is kept, so a restored backup cannot bring it back.
Over MCP
Section titled “Over MCP”A coding tool reads what applies with memory_recall, and the Memory page as you see it (active, waiting and stopped items) with memory_list. A coding tool never writes memory: add and change items in the web app. See Tools and prompts reference.