agmry

Persistent memory for AI agents — conversation history, key-value context, and semantic search across sessions. As easy as git.

git remembers your code. agmry remembers everything else.

Your agent writes great code all day — then forgets every decision the moment its context window resets. So you become the memory layer: re-explaining the project, the preferences, what broke last time. Agentic Memory is the memory your agent runs itself: one install, and it stores, recalls, and searches its own state across sessions, machines, and even other agents. It can even sign itself up — one command returns a working API key, no browser, no human.

Works with: Claude Code · Cursor · Cline · Windsurf · Aider · Codex · any MCP client

Install to full recall in 60 seconds — real terminal session, no mockups. Watch all the demos.

Install

npm install -g agmry

Quick Start

# Agent signs itself up — working key returned instantly, no card, no browser
agmry signup my-project --local

# Store memory
agmry store my-project "User prefers TypeScript strict mode and pnpm"

# New session? Recall everything
agmry recall my-project

# Half-remember something? Search it
agmry search my-project "how do we deploy"

# Full reference
agmry --help

Agents sign themselves up

No browser. No OAuth. No waiting for a human.

$ agmry signup my-project
✓ Project "my-project" created
  API key: amk_************************  (saved to .agmry/config.json)
  Live:    full access for 48h — no card, $0 today

The key works immediately — every endpoint, every tool, full access for 48 hours. Within that window, your human completes a $0 card-auth that starts the free 7-day trial on the same key. Miss the window? Nothing is deleted — the key pauses and revives the moment the card-auth completes. Add --email you@company.com and the human gets the link automatically.

Three tiers of memory — because not all memory is equal

A transcript dump isn't memory. Agents need different recall for different things:

# Short-term: ordered, role-aware conversation history (sub-ms reads)
agmry store my-project "Deployed v2.1, rolled back — migration locked the users table" -r assistant
agmry recall my-project -n 50

# Durable facts: typed key-value context — decisions, preferences, runbooks
agmry ctx my-project set deploy_flow "push image to registry, then ask infra to roll"
agmry ctx my-project get deploy_flow

# Long-term: titled, tagged knowledge entries that survive months
agmry entry my-project "Auth decision" "JWT not sessions — mobile clients can't hold cookies" --tags "arch,decisions"
agmry entries my-project --tags "decisions"

# Work-in-progress: scratchpad that's allowed to expire
agmry scratch my-project set "midway through the billing refactor, invoice.js next"

And semantic search stitches it together when the agent only half-remembers:

agmry search my-project "did we ever discuss rate limiting"
# → surfaces a months-old entry, with similarity score

Session start = one command

Instead of pasting yesterday's summary into today's prompt:

agmry boot my-project --json          # messages + context + entries, one call
agmry boot my-project --semantic "billing refactor"   # or focused on a topic

~200 tokens of structured state, not

... View full README on GitHub