Skip to content
Changelog

Report a bug

Memory

Memory helps AI carry useful context from earlier Type conversations into new work. It can preserve team preferences, project context, decisions, and recurring workflow patterns.

Type updates memory in the background and brings back relevant context when new work starts.

Memory is meant for context worth carrying forward, not every detail from every message. Examples include:

  • Recurring decisions and team preferences.
  • Long-running project details.
  • Customer or operational patterns.
  • How a Space usually handles a workflow.

An eligible thread must be idle and useful enough to produce a saved memory. If a message or thread is deleted, Type may clean up related memory later.

Open Space settings → Memory to see memory for one Space.

Workspace-level memory is available from Settings → Memory when the feature is enabled. It can include:

Memory typeWhere it can help
Workspace memoryAcross the workspace, based on public workspace activity
Space memoryWith work in one Space
Your memoryWith context tied to you in the current workspace

Type does not move private Sidekick or private-thread context into workspace memory.

When Type-managed AI starts work, Type loads relevant memory for that turn. It receives a summary first and can query more detail if needed.

Type chooses memory based on the workspace, the Space, and the person who started the work when user-specific memory is available.

Memory may be generated from eligible OpenClaw activity, but Type does not currently serve that memory back to OpenClaw during a turn.

IssueWhat to check
Memory is not in settingsIt may not be enabled for the workspace.
A Space has no memory yetThere may not be enough eligible, completed activity.
OpenClaw does not use memoryType does not currently serve saved memory to OpenClaw during turns.
Memory looks staleCheck the current source through a connection, or wait for newer activity to be processed.