Memory and knowledge
Bots remember what matters about you and your work, so you don't repeat yourself: something you tell a bot in one chat, it can recall in the next. Knowledge is different: it's documents you give a bot, such as files, a website or a GitHub repository, that it searches and cites when they're relevant.
| Memory | Knowledge | |
|---|---|---|
| What it holds | Short notes: facts, preferences, summaries of past work | Your documents, split into passages |
| Where it comes from | The bot writes it as you chat | You add sources; Casama reads them |
| How the bot uses it | The most relevant notes are in every run | The bot searches it when a question calls for it, and cites the source |
| Where to manage it | Memory | Bot profile → Knowledge |
What bots remember
Each bot has its own memory; bots never read each other's. A memory is one of these kinds:
| Kind | What it is |
|---|---|
| Fact | Something true about you, your work or the people you work with. |
| Preference | How you like things done, such as a writing style or a format. |
| Episode | A summary of an earlier part of a long conversation. |
| Summary | A summary of past work. |
Memories are written three ways:
- After every run, the bot's cheap model reads the latest exchange and saves up to 10 lasting facts and preferences. Small talk and one-off requests are skipped.
- When you ask, the bot saves a memory itself ("remember that I'm in America/Chicago"). Saving a memory never needs your approval, whatever the bot's autonomy.
- When a chat gets long, older messages are summarized once the chat's history passes about 16,000 tokens (or 70% of the model's context window, if that's smaller), and the summary is saved as an episode.
A new memory that says nearly the same thing as an existing one updates it instead of adding a copy. Without embeddings, only exact duplicates are caught.
How bots recall
At the start of every run, the bot gets the 8 memories most relevant to your message, plus every pinned memory. Casama finds them by meaning and by matching words together.
Matching by meaning needs embeddings. They use the workspace's OpenAI API key, or else the server's shared OpenRouter key (as on Casama Cloud). Without either, recall matches words only. ChatGPT plan sign-in doesn't provide embeddings.
View and edit memory
- Open a bot's chat, select More (the … button) → Bot profile, then Memory.
- Each memory shows its kind. Type in the search field to filter the list: every word you type must match, in any order.
- Open a memory's menu for:
- Pin or Unpin: pinned memories are always in the bot's context.
- Edit: change the text. The bot uses the new version the next time it's relevant.
- Delete: the memory is gone for good.
Add a memory yourself
- On the Memory screen, select Add a Memory (the + button).
- Choose Fact or Preference and write it, for example "Our fiscal year starts in April".
- Select Save.
It's stored like any memory the bot saved. Only people who manage the bot can add memories here. You can also tell the bot in chat, or import memories (below).
From the CLI:
casama memory list Ada
casama memory list Ada --search "timezone"About you
Bot memory belongs to one bot. About you belongs to you, and every bot you use reads it, in every workspace. Open it from the card at the top of Settings.
Your profile photo is set here too: tap it to Take a Photo, Choose a Photo or Remove Photo. If you signed in with Google, your Google photo is copied the first time, and Use My Google Photo brings it back. Your photo shows on your avatar and in the workspace's member list.
| Field | Where bots use it |
|---|---|
| What should bots call you? | Everywhere. Filled in from your sign-in name, and asked once in the welcome chat. |
| Pronouns (optional) | Everywhere. |
| How I like replies | Everywhere, for example "short answers, no emoji". |
| About me | Only where it's shared (see below). |
| What bots learned | Only where it's shared (see below). |
When a bot learns something about you in chat (your job, family, places, tastes), it saves it to About you instead of its own memory, which other people using that bot can see. The chat shows Saved to your profile with Undo. Facts about the work, like projects, clients and tools, stay in the bot's memory. Bots don't save health, religion, politics, sexuality or money troubles unless you ask them to remember it. To stop bots saving facts about you, turn off Learn about me from chats. You can add, edit, pin and delete facts yourself, and Import from ChatGPT or Claude fills them from another assistant's memory.
Where it's shared: About me and learned facts are used only in workspaces where you're the only member. In a team workspace they're off until you turn on Use what I've shared in … for that workspace, and they switch off by themselves when someone else joins one of your workspaces. Only you can see About you. It's in your data export and is deleted with your account. While you belong to a workspace with encryption at rest turned on, About you is encrypted with a key of your own.
Import memories from ChatGPT or Claude
If ChatGPT or Claude already knows you, bring that over.
- Open the bot's Memory screen and select the import button (Import memories from ChatGPT or Claude).
- Copy the prompt into ChatGPT or Claude, then paste its answer under Its answer and select Next.
- Casama turns the answer into facts and preferences. Untick anything that's wrong, then select Save.
Only people who manage the bot can import memories. See Templates, sharing and import for importing whole agents.
Where memory is kept
By default, memory lives in your Casama database. Workspace owners and admins can keep it in Honcho or Supermemory instead, with the workspace's own account. The memory screen, data export and account deletion work the same either way.
- Go to Settings → Workspace settings → Where memory is kept.
- Pick Supermemory or Honcho and paste the API key.
- Optional: for Honcho, a Honcho workspace (leave empty to use one made for this Casama workspace). For a self-hosted Honcho or Supermemory, its Server address.
- Turn on Copy current memories over to bring every bot's memories along, pinned ones included.
- Select Save. Casama checks the connection before saving.
To go back, open the same sheet and choose Use built-in memory again. Memories saved in the provider stay there, and built-in memories were never removed.
Warning: Honcho deletes
Honcho can't delete a single message, so deleting a memory there hides it instead of erasing it. Deleting your account deletes each bot's whole Honcho session.
Add knowledge
Give a bot documents to search and it answers from them and names the source.
- Open Bot profile → Knowledge, then Add knowledge.
- Choose what to add:
- Files: select Choose files and pick PDF, Word (
.docx), Markdown, HTML, CSV or text files, up to 50 at a time. - Website: enter the Website address. Casama reads up to 50 pages on the same site.
- GitHub: paste a GitHub link to a repository. Casama reads up to 300 of its Markdown, text, HTML and CSV files.
- Files: select Choose files and pick PDF, Word (
- Workspace owners and admins can turn on Share with every bot in the workspace.
- Select Add.
Sources are read within about a minute. Each one shows Waiting to be read, Reading…, the number of documents and passages, or why it couldn't be read. Use Sync now to read a source again, or Delete to remove it.
PDFs are read page by page, and a PDF's own title is used when it has one. A scanned PDF has no text to read, so it fails with "This PDF has no text to read, probably because it's a scan" instead of being added empty. Upload a version with selectable text.
Website crawls follow the site's robots.txt and identify as CasamaBot. Private repositories use the workspace's GITHUB_TOKEN secret (allowed for api.github.com). See Apps and connections.
How knowledge stays current
- Uploaded files are read once.
- Websites, repositories and connection sources refresh every 24 hours. Through the API you can pick any interval from 1 to 168 hours when you add a source (
sync_every_hours). - A refresh only re-embeds passages that changed, and a source with no changes isn't rewritten at all, so frequent refreshes of a site that rarely changes cost almost nothing.
- A source that fails is retried in 6 hours. One unreadable file is reported without stopping the rest.
How bots use knowledge
When a question calls for it, the bot searches its own sources and the workspace's shared ones, using the same meaning-and-words search as memory. Results come back as numbered passages with the document, where in it (a heading, a page, or rows of a CSV) and a link, and the bot is asked to cite them. In the chat, the search step lists the sources it used.
Everyone who can chat with a bot shares its knowledge, because sources belong to the bot or the workspace, not to a person. Only the bot's managers can change its sources, and only admins can change shared ones.
Encryption
With encryption at rest turned on, memories and knowledge passages are encrypted before they're stored. Search then matches by meaning, not exact words in encrypted text. See Privacy and security.
Limits
- Scanned PDFs can't be read: text recognition (OCR) isn't supported.
- Connection sources (indexing what a connected app such as Notion or Google Drive returns) work through the API only (
POST /v1/knowledge-sourceswithkind: connection). Changes in the app are picked up by the next refresh, not right away. - The app can't change how often a source refreshes, and the interval can't be changed after a source is added.
- The app can't change a website's page limit. Through the API,
max_pagesgoes up to 200. - Honcho and Supermemory catch only exact duplicate memories, not near-duplicates. Memories can't be moved back from a provider to built-in memory.
- Search in the chat shows sources on the search step, not as a separate list under the reply.