Catalog PyPI
PACKAGE EXPLORERView in registry

agent-memory-git

PyPI

Shared, git-backed memory for Claude Code and Codex.

agentsclaude-codecodexgitmemory
Versions collected1
Direct dependencies1From release 0.1.14
Last observed20 Oct, 22:41 UTC

README

Version 0.1.14 documentation

agent-memory

One memory for Claude Code and Codex.
What your agents learn, kept as plain Markdown in a git repository you own.

Live demo · Website · Docs

PyPI Python MIT license

mem ui, open in the live demo: a list of memories on the left, one open on the right with where it came from

Why agent-memory

  • Tell one agent, both remember. A preference you give Codex is there the next time Claude Code starts, and the other way round, on every machine that pulls.
  • The right memories in each session. Everything global, plus what was learned in this folder or repository, and nothing from your other projects.
  • Memory in git. One Markdown file per memory in a git repository you own, with where it came from recorded by the hooks. Every change is a commit you can review or revert; add a private remote to sync machines, or keep it all on one. Here is an example. Profiles keep separate sets of memories in repositories of their own, and a switch reaches running sessions too.
  • Nothing to run. Two hooks and git. No service, no account; search by meaning runs on your CPU.
  • A page to keep it tidy. mem ui searches by words and by meaning, edits with undo, and shows what changed week by week.

Quick start

See it first, with nothing installed:

uvx --from "agent-memory-git[ui]" mem ui --demo

Then set it up (Python 3.11+, git and uv):

uv tool install "agent-memory-git[ui]"
mem init ~/repos/agent-memory-data   # your data repository
mem install --dry-run                # every change, as a diff
mem install

Codex asks you to trust new hooks once: open /hooks in Codex and enable the three agent-memory hooks. The docs cover importing existing memories, every file mem install changes, upgrading and uninstalling.

How it works

mem install wires hooks into Claude Code and Codex; at session start they load an index from the private data repository, and at the end of each turn they commit and push new memories back

At session start a hook gives the agent an index of the memories that apply where it runs. The agent saves what is worth keeping as Markdown files, following PROTOCOL.md, and at the end of each turn a hook records where each came from, commits and pushes. The docs explain the file format, where memories load, the commands and the configuration.

Contributing

uv sync --all-extras && uv run pytest

The mem ui page is plain HTML, CSS and JavaScript with no build step, and uv run scripts/site.py serve runs the website and its live demo locally. More in the docs.

License

MIT

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 1

Collected releases
VersionPublishedDirect dependenciesOpen version
0.1.1419 Oct 20261

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
ki-seki/agent-memory

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 22:41 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:0e0b66d8f34258a783746efad5f5f6688b0b95441378a1dad3f9700f7cc794df