Memory

Memory helps Soma continue a line of thought without asking you to repeat the full background every time.

When you discuss an ongoing reorganization, a difficult working relationship, or a decision you are revisiting, relevant details from earlier chats can be available in the next conversation. Memory is scoped to you and your workspace; it does not mix your chats with a teammate’s.

How memory is used

Memory reaches a conversation in two ways:

1. Relevant context is supplied automatically. Soma looks for previous context related to your current message before she replies.
2. Soma can search deliberately. When a question calls for a more specific recall, Soma can search her memories by topic. You will see a Searching memories activity in chat.

You do not need to turn memory on for each conversation or remember where a detail was first discussed.

Ask Soma to recall something

Use the same language you used when the topic first came up. Include a person, team, project, decision, or time period when possible.

For example:

• “What did we decide about changing the leadership offsite?”
• “What patterns have I mentioned in my one-to-ones with the Product team?”
• “Bring back the options we considered for the reorganization.”

A broad prompt such as “What do you remember?” gives Soma less to search with than a specific topic.

What memory is good for

Memory works best for context that develops across conversations:

• decisions and the reasons behind them
• recurring tensions or patterns
• people and teams you work with
• goals you are tracking
• approaches you have tried
• questions you want to revisit

Use a page instead when you need a document that you can edit, organize, share, or treat as a source of record. Memory supports continuity; pages hold material you want to maintain directly.

Review what Soma used

Expand the Searching memories activity in chat when you want to understand the direction of a lookup.

If Soma recalls something incorrectly, correct it in the conversation. Do not assume that a recalled detail is current simply because it came from an earlier chat.

Privacy and current limits

• Memory is private to you within the current workspace.
• Sensitive text is stored in de-identified form. Workspace privacy controls determine which categories Soma can read in clear form when memory is retrieved.
• There is no memory browser. You cannot currently inspect, edit, or delete individual memories from a list in the app.
• Recall is selective. Soma may not surface every earlier detail, especially when the current prompt is broad or uses different language.
• Memory builds from your use of chat; a new workspace has little previous context to retrieve.

Related features

• Chat is where memory is created and used.
• Pages are better for deliberate, editable reference material.
• Privacy controls how sensitive values appear when Soma retrieves stored context.
• Knowledge base provides specialist material; memory provides your personal and organizational context.