01

Quick Start

Use Console after you have a mem9 account or an API key you want to manage.

  • Open mem9 Console from the Log in menu and sign in with your account.
  • Choose the organization and project from the shell before changing resources.
  • Use Install mem9 when you need the official OpenClaw onboarding prompt.
  • Use Claim API key when you already have a mem9 API key and want to attach it to a Space.
  • Open Space or Memories to review what your agents are storing.

02

Organization, Project, and Space

Console groups resources so a team can manage memory without mixing every key together.

Organization

An organization owns billing, usage, settings, and member-level permissions. The sidebar organization selector changes which organization you are operating in.

Project

A project is the working container for spaces and Space Chains. Use the project switcher in the header to move between products, environments, or teams.

Space

A Space is the unit that receives a mem9 tenant API key. Your agents write and recall memories through that key, while Console uses the Space to show metrics, keys, imports, and memory tools.

03

Install mem9 and Claim API Keys

There are two common onboarding paths.

Install mem9

  • Open Install mem9 in the sidebar.
  • Copy the onboarding prompt into OpenClaw.
  • Follow SKILL.md to provision or reconnect a hosted mem9 API key.
  • Return to Console when you want to inspect spaces and memory activity.

Claim an existing API key

  • Open the claim flow when you already have an anonymous or previously generated mem9 API key.
  • Choose an organization, project, and destination Space.
  • Create a new Space or attach the key to an existing Space without an active key.
  • After a successful claim, open that Space to inspect the key and memory data.

04

Spaces

The Space page is the project-level list of memory spaces.

  • Create a Space for a product, environment, agent group, or isolated memory boundary.
  • Use the table to compare names, descriptions, and whether each Space already has an API key.
  • Open a Space by selecting its name.
  • Use the row actions to edit the Space, configure or replace its key, or delete it when it is no longer needed.

05

Space Detail

Space detail is where a Space becomes operational.

Tenant key

  • Configure a key before expecting memory data to load.
  • Reveal and copy an active key only when your role can manage the Space.
  • Treat revealed keys as secrets; Console shows masked keys by default.

Metrics and imports

  • Use metric cards to check total, pinned, and insight memories.
  • Use the latest import panel to see whether imports are running, completed, or failed.
  • Use the Space switcher to compare another Space without returning to the list.

Memory workbench

  • Create a memory directly from Console.
  • Turn on Smart ingest when you want Console to extract durable facts from a pasted message.
  • Edit, delete, bulk delete, filter, sort, and refresh active memories.
  • Use appId when you need to isolate memories within the same Space key.

06

Memories

The Memories page is a project-level explorer for one selected Space.

  • Pick a Space from the header selector.
  • Filter by text, type, state, agent, tags, or appId.
  • Open a memory to inspect content, metadata, tags, score, confidence, session, agent, version, and timestamps.
  • If the selected Space has no key, open Space key settings before browsing memories.

07

Space Chains

A Space Chain lets one chain key recall across several Spaces in a controlled order.

Create or import

  • Create Space Chain to start a new chain in the current project.
  • Import key when you already have a chain key and want Console to manage or test it.
  • Open a chain to edit its details, keys, nodes, and memory tools.

Nodes and routing

  • Add Spaces that already have active keys.
  • Move nodes up or down to control recall order.
  • Save node order before depending on chain recall.
  • Use routing policy prompts on nodes when a Space should only be searched for certain kinds of questions.

Chain keys and testing

  • Create or bind chain keys from the detail page.
  • Disable a chain key when it should no longer be used.
  • Use the recall and memory tools to compare chain behavior with a single Space.

08

Usage, Billing, and Settings

These pages operate at the organization level.

Usage

  • Review memory recall and memory write request usage.
  • Change the date range, inspect daily trends, and page through usage events.
  • Use event rows to understand source, API key, agent, included usage, and on-demand usage.

Billing

  • Review the current plan, subscription period, included launch access, and on-demand settings.
  • Payment, subscription, and invoice actions may appear as coming soon depending on the rollout state.

Settings

  • Use Settings for account and organization-level management as Console evolves.
  • Use the account menu for theme, language, and logout.

09

Safe Operations

Console exposes powerful controls, so treat changes deliberately.

  • Do not reveal or copy API keys unless you are about to configure a trusted client.
  • Check delete previews and confirmation dialogs before deleting Spaces or Space Chains.
  • Use separate Spaces for data that should not be searched together.
  • Use appId filters when a single key serves multiple applications.
  • When memory results look wrong, first check the selected organization, project, Space, key status, and appId filter.