alejandroqh

Memory39 — AI skill for Claude Code

AI community

One binary, One local file.

How to install Memory39

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

What Memory39 does

One binary, One local file. Shared memory system for AI agents

Alternatives in AI

Memmy Agent — 🍙 A personal AI agent & local memory hub for all AI agents, gives every AI one shared, fully controlled memor 1k ★
Iai Personal Memory Engine — A cyber brain for your AI 866 ★
Wax — Shared Single-file memory layer for all your agents, sub mili-second RAG over text, photo and video on Apple S 791 ★

README

▄▄▄▄  ▗▞▀▚▖▄▄▄▄   ▄▄▄   ▄▄▄ ▄   ▄ ▄▄▄▄ ▄▄▄▄ 
█ █ █ ▐▛▀▀▘█ █ █ █   █ █    █   █    █ █  █ 
█   █ ▝▚▄▄▖█   █ ▀▄▄▄▀ █     ▀▀▀█ ▀▀▀█ ▀▀▀█ 
                            ▄   █ ▄▄▄█ ▄▄▄█ 
                             ▀▀▀

**One binary. One local SQLite file. One memory, shared by every MCP client on your machine.**

memory39 is a Rust CLI + MCP server backed by SQLite + FTS5. Every MCP-capable AI tool on your machine (Claude Code, Claude Desktop, Codex, OpenCode, OpenClaw) reads and writes the same `~/.memory39/memory39.db`, so a fact learned in one client is instantly recallable from any other. No cloud, no daemon, no sync.

Results are ranked by temporal-priority scoring: **0.4 x relevance + 0.3 x importance + 0.3 x recency** (30-day half-life), so recent important matches surface first.

Why memory39

Persistent across sessions: memories live in an on-disk SQLite file and survive restarts, CLI invocations, and MCP reconnects.
One knowledge base across every MCP client: Claude Code, Claude Desktop, Codex, OpenCode, and OpenClaw all point at the same ~/.memory39/memory39.db. A fact stored from Claude is instantly recallable from Codex; a person stored via the CLI shows up in every MCP client. No syncing, no duplication.
Local and private: no cloud, no account, no telemetry. Your memory is a single SQLite file on your machine that you can inspect, back up, or move by copying.
Single binary, zero daemon: CLI for scripting (memory39 recall ...), MCP server on demand (memory39 mcp). Nothing runs in the background between calls.
Portable DB path: point at a different database by exporting MEMORY39_DB=/path/to/other.db (supports ~/ expansion). Useful for project-scoped memory or isolated benchmarks.
Cross-type discovery: the connect command links concepts across events, things, persons, and places in a single query, so relationships surface even when facts are stored as different memory types.