MeetAndy logo

Memory

How Andy remembers facts about your Space, how to teach Andy, and how to view and edit what it knows.

Memory is a set of short notes Andy keeps for each Space: your conventions, decisions, ongoing work, and background. Andy reads these notes before every task, so you say something once and it carries across conversations.

What memory holds

Notes are grouped into sections:

  • Rules. Guidelines Andy follows when completing tasks.
  • Projects. Work your team is doing now. Andy reads them when a task touches that work.
  • Areas. Ongoing responsibilities your team keeps up. Andy checks them to work the way you do.
  • Resources. Background notes Andy looks up when a task needs them.
  • Unsorted. Notes Andy can read and files in the right place over time.
  • Archive. Older notes Andy only opens when a task asks about the past.

Memory does not keep every message, plan, or pull request. Those already live in Slack, GitHub, or Jira. It keeps the facts worth remembering across conversations.

What to addWhat not to add
"We use PostgreSQL 17 in production."Past plans and pull requests.
"Our release freeze starts on the 25th."Casual Q&A from weeks ago.

How notes get into memory

  • You tell Andy. Ask Andy to remember something in Slack, Google Chat, or a task in the web app. See Teach Andy in chat.
  • Andy reads your code. When you create a Space, Andy reads the connected repositories to write the first notes. You can run Rescan code again later. See Rescan code.
  • Andy learns from finished tasks. When a task wraps up, Andy may add what it learned about how your team works. Each note shows where it came from, and you can undo any of them. See History, undo, and restore.
  • You edit it on the web. See View and edit memory.

Teach Andy in chat

You can add to memory without opening the web app. Mention Andy in Slack or Google Chat, or write in a task, and say what to remember.

@MeetAndy remember that the project deadline is March 15th
@MeetAndy remember we use Tailwind 4 with CSS-first config

Andy replies once the note is saved. It files the note in the right section and, if the new fact changes an older note, updates that note instead of keeping both.

To check what Andy knows, ask a question the same way:

@MeetAndy what's our release freeze date?

If memory has the answer, Andy replies with it. If not, Andy treats the question like any other request.

There is no "forget this" command in chat. To remove or fix a note, edit it on the web as described below.

View and edit memory

Open Space settings for your Space and choose Memory. Everyone with access to the Space can read memory. Space members and company admins and managers can change it.

The Memory page in Space settings, open on Overview

Browse memory

The page opens on Overview: a short summary of the Space, the files Recently updated, and each section with a one-line description of every file. Click a line to open the file. The file tree on the left and Search memory help you jump straight to a note.

Add to memory

Click + (Add to memory) next to the search box, write what you want Andy to remember, and click Add to memory. Andy files it in the right place and updates the page when it's done.

Edit a note

Open a file, click ⋯ at the top right, and choose Edit. In Edit memory, describe what you'd like to update, correct, or add, then click Save changes. Andy makes the change.

Delete a file

Open the file, click ⋯, and choose Delete. The file is removed and Andy stops using it in future tasks. If other files link to it, those links become plain text, and the dialog lists them before you confirm.

History, undo, and restore

Every change is kept. Click the last-updated time at the top of a file (for example, "1w ago") to open Version history and see what changed, when, and where it came from, such as "Updated from a Slack message" or "Updated from a finished task".

  • Restore this version in Version history brings back an earlier version of the file.
  • Undo this change puts the files back to how they were before one change. When Andy saves a new note, its New memory saved message has a See what changed link that opens the change, with Undo this change on it. History keeps the change.

When you look at an older version, the page shows memory as of that date. Andy still uses the latest memory.

Changes that need review

If two people change the same note at the same time, Andy sets the conflicting change aside and marks the file Needs review. Andy doesn't use the set-aside change until it's resolved.

Rescan code

Click Rescan code (the circular arrows icon next to the search box) to have Andy read the connected repositories again. Andy re-checks the notes it already wrote from your code and keeps only the ones worth keeping. A banner shows progress while Andy reads. Space members and company admins and managers can run it.

Tips

  • Memory is per Space. A note in one Space doesn't carry over to another. Add it to both if it applies to both.
  • Keep notes short and concrete. "We use Postgres 17" helps. "We try to write good code" doesn't.
  • Memory is shared. Everyone with access to the Space can read it, so don't put anything sensitive in it.