Enlightened-Republic

Sharpwave — AI skill for Claude Code

AI community

Long-term memory for AI agents — forgets on purpose, consolidates the rest.

How to install Sharpwave

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Enlightened-Republic/sharpwave and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Sharpwave does

Long-term memory for AI agents — forgets on purpose, consolidates the rest. Ships as the sharpwave MCP server (Claude Code, Cursor, Claude Desktop) and the openwave OpenClaw plugin (runs in-process, auto-injects memory into every turn).

Alternatives in AI

  • Hindsight — State-of-the-art long-term memory for AI agents by Vectorize 6.7k ★
  • LongHorizon Harness — The long-horizon computer-use harness 1.3k ★
  • Nocturne Memory — A lightweight, rollbackable, and visual Long-Term Memory Server for MCP Agents 1.3k ★

README

Sharpwave

**A long-term memory MCP server for AI agents.** It remembers across sessions, forgets what stops mattering, and consolidates the rest — modeled on how human memory actually works, not a vector store with extra steps.

npx -y sharpwave

Works with Claude Code, Claude Desktop, Cursor, and any other MCP client.

**Building on [OpenClaw](https://openclaw.ai)?** Use **[openwave](packages/openwave/README.md)** instead — the same engine as a native OpenClaw plugin. It does everything this MCP server does, *plus* it injects the relevant memories into every agent turn automatically (no tool call) and runs the sleep system in-process. Install: `openclaw plugins install clawhub:openwave`. openwave is packaged separately — see [`packages/openwave/`](packages/openwave/).


Repository layout

npm-workspaces monorepo:

  • packages/core — sharpwave-core, the memory engine (retrieval, consolidation, extraction, the FSRS forgetting curve, the graph). Published to npm as the shared engine behind both sharpwave and openwave.
  • packages/mcp — sharpwave, the stdio MCP server published to npm. This is what npm i sharpwave / npx -y sharpwave installs.
  • packages/openwave — the OpenClaw plugin. Being moved to its own repo (Enlightened-Republic/openwave) and published independently; it lives here for now. See `packages/openwave/README.md`.

`sharpwave-core` is bundled into each consumer at build time, so `sharpwave` and `openwave` always ship the exact engine they were built against — there is no version-skew path between them. It is a **devDependency** of both consumers, not a runtime one — esbuild inlines it, and a runtime dep on an unpublished package would break every `npm install sharpwave`.

`npm run test:pack` is the pre-publish gate: it packs `sharpwave`, installs the tarball in a clean workspace-free directory (where a stray runtime dep on `sharpwave-core` would 404),