getmem.ai Memory

v1.0.3

Persistent memory for every user via getmem.ai. Automatically ingests conversations and injects relevant context before each agent reply. Two API calls. $20...

⭐ 0· 122·0 current·0 all-time

by@nimblev2023

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for nimblev2023/getmem-openclaw.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "getmem.ai Memory" (nimblev2023/getmem-openclaw) from ClawHub.
Skill page: https://clawhub.ai/nimblev2023/getmem-openclaw
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install getmem-openclaw

ClawHub CLI

Package manager switcher

npx clawhub@latest install getmem-openclaw

Security Scan

Capability signals

Requires sensitive credentials

These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

Name/description, README, SKILL.md, package.json, and the compiled/source code all describe a memory plugin that calls getmem.ai's /v1/memory/get and /v1/memory/ingest endpoints. The plugin requires a getmem API key via plugin config (not an environment variable), which is appropriate for this function. Minor inconsistencies (small variations in IDs/names across dist/src files and an odd SKILL.md frontmatter 'install' entry referencing 'kind: pip' for an npm package) appear to be documentation/metadata quirks rather than functional mismatches.

ℹ

Instruction Scope

Runtime hooks only read message context/session keys and perform two external API calls per exchange (fetch memory before reply and ingest the exchange after reply). They do not read unrelated files, env vars, or system config. This behavior is within the stated scope but it does mean all user messages and assistant replies (and user identifiers) are transmitted to the external service — a privacy-sensitive action that is expected for a memory plugin.

ℹ

Install Mechanism

Registry shows this as an instruction-only plugin (no platform install spec), but the package includes full source, package.json, and a package-lock that references an npm package 'getmem-ai'. There is no high-risk remote download URL in the manifest. The SKILL.md frontmatter has an inconsistent 'install' block (id: npm-getmem-ai, kind: pip) which is likely a documentation mistake. Overall install mechanism is standard for OpenClaw plugins and not unusual.

ℹ

Credentials

The plugin asks for a single getmem API key (via plugin config), which is proportional to its function. However, the plugin will transmit user IDs and full message content to an external service (default baseUrl https://memory.getmem.ai). That data flow is expected but has privacy and compliance implications — there are no unrelated credentials requested.

✓

Persistence & Privilege

The plugin does not set always:true and does not request elevated platform privileges. It registers hooks (message:received and message:sent) within normal plugin behavior and does not modify other plugins or global agent settings beyond its own config.

Assessment

This plugin appears to be what it claims: it sends user messages and assistant replies (plus user identifiers) to getmem.ai and injects returned memory into the agent prompt. Before installing: 1) Be aware all conversation content forwarded to getmem.ai will be stored/used by that external service — review getmem.ai's privacy and security policies and the API key provisioning. 2) Do not enable this for channels or users that exchange sensitive or regulated data unless you have accepted the external storage risk. 3) Verify the plugin config (apiKey and baseUrl) points to the official getmem endpoint; changing baseUrl would redirect data to whatever endpoint you configure. 4) The repository contains source — you can audit the included files (dist/src) yourself; the code shows no hidden endpoints or unrelated credential access. 5) If unsure, test in an isolated environment or disable (enabled: false) until you’ve confirmed compliance with your data-handling policies.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🧠 Clawdis

latestvk977pyv9s7ycxzcdw4kghr258s8550ew

122downloads

0stars

3versions

Updated 1w ago

v1.0.3

MIT-0

getmem.ai Memory Plugin for OpenClaw

Gives your OpenClaw agent persistent memory via getmem.ai.

Install

openclaw plugins install clawhub:@getmem/openclaw-getmem
openclaw config set plugins.openclaw-getmem.apiKey gm_live_...
openclaw gateway restart

Get your API key at platform.getmem.ai — $20 free credit on signup.

How it works

Before each reply — fetches memory context for the user and injects it into the agent prompt
After each reply — ingests the exchange into getmem for future retrieval

Memory accumulates automatically. No code changes needed.

Comments

Loading comments...