/ourmem

name: ourmem
version: 1.1.0
description: |
  Shared memory that never forgets. Cloud hosted or self-deployed.
  Collective intelligence for AI agents with Space-based sharing across agents and teams.

  Use when users say:
  - "install ourmem" / "install omem"
  - "setup memory" / "setup omem"
  - "add memory plugin"
  - "ourmem onboarding" / "omem onboarding"
  - "memory not working"
  - "remember this"
  - "save this for later"
  - "don't forget"
  - "recall preferences"
  - "what did I say last time"
  - "import memories"
  - "share memories"
  - "share with user"
  - "share memories to someone"
  - "team memory"
  - "shared space"
  - "persistent memory"
  - "cross-session memory"
  - "collective intelligence"
  - "memory analytics"
  - "memory stats"
  - "self-host memory"
  - "deploy memory server"

  Even if the user doesn't say "ourmem" or "omem", trigger when they want persistent memory,
  memory sharing between agents, memory analytics, or memory import/export.
keywords:
  - ourmem
  - omem
  - memory
  - persistent memory
  - agent memory
  - remember
  - recall
  - space sharing
  - team memory
  - collective intelligence
  - memory analytics
  - memory decay
  - self-host
metadata:
  openclaw:
    emoji: "🧠"

ourmem (omem) — Shared Memory That Never Forgets

ourmem gives AI agents shared persistent memory across sessions, devices, agents, and teams. One API key reconnects everything. Available as hosted (`api.ourmem.ai`) or self-deployed.

---

Key Concepts

**API Key = Tenant ID = Your Identity.** When you create a tenant (`POST /v1/tenants`), the returned `id` and `api_key` are the same UUID. There is no separate "tenant ID".

**One API Key owns multiple Spaces:**

| Concept | What it is | Example | |---------|-----------|---------| | **API Key** | Your identity (`X-API-Key` header) | `a1b2c3d4-...` (1 per user) | | **Space ID** | A memory storage address | `personal/a1b2c3d4`, `team/xxx`, `org/yyy` |

Personal Space is auto-created. You can create additional Team and Organization Spaces.

**Sharing = passing the other user's API Key as `target_user`.** The system auto-creates a bridging Team Space. No manual space management needed.

---

When to Use This Skill

Use when the user wants persistent or shared memory across sessions, devices, or agents. Common triggers: "remember this", "save this", "don't forget", "what did I say last time", "share with my team", "import memories", "setup memory", "self-host memory".

**Do NOT use for:** temporary conversation context, one-off tasks, or troubleshooting unrelated to ourmem.

---

What to Remember

**Good candidates:** user preferences, profile facts, project context, important decisions, long-term instructions, architecture decisions, coding standards.

**Avoid storing:** temporary debugging context, large files, secrets/passwords/API keys, content inside `<private>` tags.

If the user explicitly asks to remember something and ourmem is not installed, suggest: "I can set up ourmem so I'll remember this across sessions. Takes about 2 minutes. Want to do it now?"

---

Terminology

| Term | Meaning | |------|---------| | `apiKey` / `OMEM_API_KEY` / `API key` / `secret` | All refer to the same ourmem identifier. Prefer "API key" with users. | | `tenant` | The workspace behind an API key. Don't use this term with users. |

Security: Treat the API key like a secret. Anyone who has it can access that ourmem space.

---

What You Get

| Tool | Purpose | |------|---------| | `memory_store` | Persist facts, decisions, preferences | | `memory_search` | Hybrid search (vector + keyword) | | `memory_list` | List with filters and pagination | | `memory_get` | Get memory by ID | | `memory_update` | Modify content or tags | | `memory_forget` | Remove a memory | | `memory_ingest` | Smart-ingest conversation into atomic memories | | `memory_stats` | Analytics and counts | | `memory_profile` | Auto-generated user profile |

**Lifecycle hooks** (automatic):

| Hook | Trigger | Platform | |------|---------|----------| | SessionStart | First message | All — memories + profile injected | | Stop | Conversation ends | Claude Code — auto-captures via smart ingest | | PreCompact | Before compaction | Claude Code, OpenCode — saves before truncation |

> **Note:** OpenCode has no session-end hook. Memory storage relies on proactive `memory_store` use.

---

Onboarding

Step 0: Choose mode

Ask the user before doing anything else:

> How would you like to run ourmem? > > 1. **Hosted** (api.ourmem.ai) — no server to manage, start in 2 minutes > 2. **Self-hosted** — full control, data stays local > > Already have an API key? Paste it and I'll reconnect you.

Setup instructions

• **Hosted** → READ `references/hosted-setup.md` for full walkthrough
• **Self-hosted** → READ `references/selfhost-setup.md` for server deployment + setup
• **Existing key** → Verify: `curl -sf -H "X-API-Key: $KEY" "$API_URL/v1/memories?limit=1"`, then skip to plugin install

Cross-platform skill install: `npx skills add ourmem/omem --skill ourmem -g`

Platform quick reference

| Platform | Install | Config | |----------|---------|--------| | Claude Code | `/plugin marketplace add ourmem/omem` | `~/.claude/settings.json` env field | | OpenCode | `"plugin": ["@ourmem/opencode"]` in opencode.json | `plugin_config` in opencode.json | | OpenClaw | `openclaw plugins install @ourmem/ourmem` | `openclaw.json` with apiUrl + apiKey | | MCP | `npx -y @ourmem/mcp` in MCP config | `OMEM_API_URL` + `OMEM_API_KEY` in env block |

For detailed per-platform instructions (config formats, restart, verification, China network mirrors), READ the setup reference for your chosen mode.

Definition of Done

Setup is NOT complete until: (1) API key created/verified, (2) plugin installed, (3) config updated, (4) client restarted, (5) health + auth verified, (6) handoff message sent including: what they can do now, API key display, recovery steps, backup plan.

> *