OpenClaw Integration Guide

Use the Awareness Memory plugin to give OpenClaw persistent, structured memory across sessions and tools.

What this plugin adds

The @awareness-sdk/openclaw-memory plugin provides:

Long-term memory across OpenClaw sessions
Structured context loading before work starts
Automatic capture after work ends
Shared memory between OpenClaw, Claude Code, Cursor, Windsurf, and SDK-based agents

The plugin now exposes the current Awareness tool family:

Tool	Purpose
`__awareness_workflow__`	Always-visible workflow guide
`awareness_init`	Start a session and load context
`awareness_recall`	Hybrid semantic + keyword search
`awareness_lookup`	Fast structured lookup for tasks, risks, knowledge, and timeline
`awareness_record`	Unified write path for events, batches, task updates, and insight submission

Quick Start

Option A: One-click install prompt

The Awareness OpenClaw page can generate a prompt with your API key, memory ID, and role already filled in. Paste that prompt into OpenClaw and let the agent:

Download the plugin archive
Install the plugin
Update ~/.openclaw/openclaw.json
Verify the plugin with openclaw plugins list
Clean up the downloaded archive

This is the fastest public setup path if you already know which memory to connect.

Option B: Manual install

openclaw plugins install @awareness-sdk/openclaw-memory

For local development:

openclaw plugins install -l ./sdks/openclaw

Manual Configuration

Edit ~/.openclaw/openclaw.json:

{
  "plugins": {
    "slots": {
      "memory": "memory-awareness"
    },
    "entries": {
      "memory-awareness": {
        "enabled": true,
        "config": {
          "apiKey": "aw_your-api-key",
          "baseUrl": "https://awareness.market/api/v1",
          "memoryId": "your-memory-id",
          "agentRole": "builder_agent",
          "autoRecall": true,
          "autoCapture": true,
          "recallLimit": 8
        }
      }
    }
  }
}

Get the API key and memory ID from the Awareness dashboard.

Recommended Workflow

Session start

Call:

awareness_init(source="openclaw")

This returns:

session_id
recent narratives
open tasks
top knowledge cards

Before implementing

Call:

awareness_recall(semantic_query="...", keyword_query="...")

Use this to check prior decisions, fixes, or user preferences before making changes.

During work

After every meaningful change, record it:

awareness_record(action="remember", text="WHAT / WHY / OUTCOME / FILES")

Session end

Write a summary:

awareness_record(action="remember_batch", steps=[...])

If a write returns _extraction_instruction, pass that instruction to your client LLM and submit the extracted result with:

awareness_record(action="submit_insights", content=<result>)

Auto Features

Auto Recall

When autoRecall is enabled, the plugin:

Loads session context before the agent starts
Builds a hybrid search query from the user prompt
Injects relevant context into the agent run

Auto Capture

When autoCapture is enabled, the plugin:

Collects the meaningful part of the conversation
Removes injected memory blocks
Stores a concise summary after the run

This gives you a low-friction default setup even if the agent forgets to call the write tools manually.

Configuration Reference

Field	Type	Default	Description
`apiKey`	string	required	Awareness API key
`memoryId`	string	required	Connected memory ID
`baseUrl`	string	`https://awareness.market/api/v1`	Awareness API base URL
`agentRole`	string	`builder_agent`	Scoped role name
`autoRecall`	boolean	`true`	Load context automatically before each run
`autoCapture`	boolean	`true`	Save a summary automatically after each run
`recallLimit`	integer	`8`	Result limit for recall

Why use Awareness with OpenClaw

You keep one memory across OpenClaw, Claude Code, Cursor, Windsurf, and SDK workers.
You can store project decisions, pitfalls, tasks, and handoff context in one place.
The plugin supports both explicit tool usage and auto-recall/auto-capture hooks.
Multi-role memories let builder, reviewer, and specialist agents share the same project with role-specific context.

Troubleshooting

Plugin not found

Run openclaw plugins list
Confirm the plugin was installed successfully
For local development, verify the path passed to openclaw plugins install -l

No context returned

Check apiKey and memoryId
Confirm the memory actually contains data
Make sure the configured baseUrl points to your Awareness API

Tools missing in the agent

Restart OpenClaw after changing openclaw.json
Confirm the memory slot points to memory-awareness
Check logs for plugin initialization errors

One-click install failed

Re-run the prompt and include the terminal error
If necessary, fall back to manual installation and config

Documentation