omem 永不遗忘记忆库

musl static build (portable, zero dependencies)

Single binary that runs on any Linux x86_64 — no glibc, no libraries, nothing.

```bash rustup target add x86_64-unknown-linux-musl

RUSTFLAGS="-C target-feature=+crt-static -C relocation-model=static" \ cargo build --release --target x86_64-unknown-linux-musl \ -p omem-server --no-default-features

Run (no dependencies needed)

ssh user@server "gunzip /opt/omem-server.gz && chmod +x /opt/omem-server && /opt/omem-server" ```

🔧 I'm building AI products

REST API with 48+ endpoints. Docker one-liner for self-deploy. Embed persistent memory into your own agents and workflows.

→ Jump to Self-Deploy

</td> </tr> </table>

Agent Install (recommended)

One message to your AI agent. It handles everything — API key, plugin install, config, verification.

Hosted (ourmem.ai — nothing to deploy):

Self-hosted (your own server):

That's it. Your agent handles the rest.

Skill Install (alternative):

If you prefer CLI installation, install the ourmem skill directly:

npx skills add ourmem/omem --skill ourmem -g

This works with 44+ AI agents including Claude Code, OpenCode, Cursor, and more. See Vercel Skills CLI for details.

---

<details> <summary><b>Manual Install</b> (without agent assistance)</summary>

2. Install Plugin

OpenCode: Add "plugin": ["@ourmem/opencode"] to opencode.json + configure plugin_config with apiUrl and apiKey in the same file.

Claude Code: /plugin marketplace add ourmem/omem + set env vars in ~/.claude/settings.json.

OpenClaw: openclaw plugins install @ourmem/ourmem + configure openclaw.json with apiUrl and apiKey.

MCP (Cursor / VS Code / Claude Desktop):

{
  "mcpServers": {
    "ourmem": {
      "command": "npx",
      "args": ["-y", "@ourmem/mcp"],
      "env": {
        "OMEM_API_URL": "https://api.ourmem.ai",
        "OMEM_API_KEY": "your-api-key"
      }
    }
  }
}

Self-Deploy

```bash

Build from Source

Two build modes

glibc build (with Bedrock support)

```bash cargo build --release -p omem-server

Quick Start

Object Storage (Optional)

By default ourmem stores data on local disk. For durability and scalability, configure AWS S3 or any S3-compatible object storage:

```bash

Add to your environment

OMEM_S3_BUCKET=your-bucket # enables s3:// scheme AWS_ENDPOINT_URL=https://s3.amazonaws.com AWS_REGION=us-east-1

API Key = Tenant ID = Your Identity

When you create a tenant, the returned id is your API Key. They're the same UUID. There is no separate "tenant ID".

```bash curl -X POST https://api.ourmem.ai/v1/tenants -d '{"name": "alice"}'

→ {"id": "a1b2c3d4-...", "api_key": "a1b2c3d4-...", "status": "active"}

Sharing = Passing Your API Key

To share memories with another user, you pass their API Key as target_user:

```bash

Share all your preferences to user Bob

curl -X POST https://api.ourmem.ai/v1/memories/share-all-to-user \ -H "X-API-Key: your-api-key" \ -d '{"target_user": "bobs-api-key", "filters": {"categories": ["preference"]}}' ```

The system automatically creates a bridging Team Space between you and Bob. No manual space management needed.

1. Get an API Key

Hosted:

```bash curl -sX POST https://api.ourmem.ai/v1/tenants \ -H "Content-Type: application/json" \ -d '{"name": "my-workspace"}' | jq .

→ {"id": "xxx", "api_key": "xxx", "status": "active"}

**Self-deploy:**

Save the returned api_key — this reconnects you to the same memory from any machine.

Minimal (BM25 search only, no embedding API needed)

docker run -d -p 8080:8080 ghcr.io/ourmem/omem-server:latest

API at a Glance

Full API reference (48+ endpoints): docs/API.md

API Key vs Space ID

One API Key owns multiple Spaces:

API Key "a1b2c3d4"
  │
  ├── personal/a1b2c3d4     ← auto-created, your private memories
  ├── team/e5f6g7h8          ← team space you created (you = Admin)
  ├── team/i9j0k1l2          ← team space you were invited to (you = Member)
  └── org/m3n4o5p6           ← organization you joined (you = Reader)

Alternative: OSS-compatible storage

OMEM_OSS_BUCKET=your-bucket # enables oss:// scheme OSS_ENDPOINT=https://oss-xx-internal.aliyuncs.com OSS_ACCESS_KEY_ID=your-ak # or use ECS RAM role (auto-discovered) OSS_ACCESS_KEY_SECRET=your-sk ```

If both OMEM_S3_BUCKET and OMEM_OSS_BUCKET are set, OSS takes priority.