Memory for developers
Tell it once. It remembers.
Most developers explain the same things to every new chat. Say once what you work on and how you want a pile of runbooks and notes written up, and the agent keeps it for every chat after, in a list you can read and edit.
Saved from what you say in chat, with no form to fill in
Every memory is a plain sentence you can read, edit or delete in settings
Tell it to forget something and it is gone
One switch turns memory off, and nothing about you reaches the model while it is off
Facts caught on the way past
Say you run a bakery while asking about customers. The bakery is kept and the question is answered.
Read it, fix it, delete it
The whole list lives in Settings under Personalization, as sentences rather than a black box.
Forget is a real command
Say forget that in the chat and the memory is deleted, not hidden.
Off means off
Turn memory off and no memory text goes out with a chat, on any device.
The phone knows what the laptop learned
Memories travel with your settings, so with sync on there is one list on every device.
Replies already in your voice
With your base style and standing instructions, the answer arrives the way you would have written it.
Results
Three things that stop being a problem
Feature lists are easy to write and hard to care about. This is what changes for developers.
Stop solving the same bug twice
Describe the symptom in search and get the note where you already worked it out.
Keep decisions where you can defend them
Ask what you decided about a service and get the note, the date and the reasoning.
Point the AI at your own stack
Bring your own key, or run a local model through Ollama, and keep the workspace on disk.
In practice
What that looks like for developers
A few moments in a normal week where the app earns its place.
Debugging
Write the symptom, the theory and the fix in one note, with the log you kept attached.
Architecture review
Record the conversation and keep the decision log next to the diagram.
New project
Keep the setup steps in a runbook that actually gets found again.
The rest of the app
What Else Grape Does
Every part of the app is built around the same idea: keep what you write, and hand it back when you need it.
AI Agent
Chat that reads your library and can act on it
Open
Semantic search
Search that works on what you meant
Open
Voice and transcription
Meetings and lectures become searchable text
Open
Web clipper
Save any page from Chrome into a note
Open
Share to Grape
A page from the share sheet becomes a note
Open
Flashcards
Decks built from the notes you wrote
Open
Find it next time it breaks.
Runbooks, architecture decisions and the fix you worked out at midnight, in a local library you can search by meaning and keep offline.