Memory
Keep durable, searchable context attached to the right member and organization across agent clients.
Memory preserves the part of an agent setup that should outlive a client or conversation. A user can move from Claude Code to Codex—or replace the agent entirely—without rebuilding stable preferences, facts, and project decisions.
The organization owns the brain. Each write is scoped as shared or private inside that organization, and CoreSpeed derives the caller identity from auth; the agent cannot supply a different user ID to cross the boundary.
Seven public tools
Names below are the operations exposed on the unified MCP surface:
| Tool | Use it for |
|---|---|
memory__remember | Save one concise fact, preference, or decision. |
memory__search_memory | Find memories relevant to the current task. |
memory__ingest | Extract durable memories from recent messages. |
memory__update_memory | Correct an existing memory by ID. |
memory__delete_memory | Remove one memory. |
memory__list_memory | List recently saved memories. |
memory__clear_all_memory | Delete all memory after explicit confirmation. |
The broader gbrain browse surface is still hidden from public MCP discovery.
Operations such as page listing, graph traversal, backlinks, and hybrid query
will be documented only after their tenant-scoping checks pass and their tools
appear in tools/list.
Shared and private context
memory__remember accepts scope: "shared" | "private":
sharedis the default and can be read by agents operating inside the same organization boundary.privatecan be read only for the member who created it.
Member state is always organization-scoped. Turning memory off in one organization cannot affect the same user in another organization.
Pricing and holds
Memory operations cost $0 per call. The provider remains inside the metered operating boundary, so an organization billing hold or suspension can still block execution. Storage quotas and rate limits protect the shared service.
Inspect and remove memory
Use Dashboard → Memory to browse memories, search, inspect the graph, open a detail view, and delete content. Disabling the memory capability hides its MCP tools but preserves existing data; deletion is a separate explicit action.
What belongs in memory
Save context that will improve a later action: a preference, a product decision, a named relationship, or an operating constraint. Do not use memory as a transcript archive, a secret store, or a substitute for application data.