Project Memory Python Packages

keep-the-why-dashboard

The why layer of repo-native project memory: the reasoning behind a codebase as Markdown in the repo, versioned by Git, for coding agents and humans, so nothing rejected is proposed twice. No database, no daemon, no account.

keep-the-why-lint

The why layer of repo-native project memory: the reasoning behind a codebase as Markdown in the repo, versioned by Git, for coding agents and humans, so nothing rejected is proposed twice. No database, no daemon, no account.

pagelore

Durable project memory for AI coding agents (Claude Code, Codex, Cursor, Gemini CLI): decisions and bug post-mortems as markdown pages in your repo, BM25F search via CLI or MCP server, validated writes. No server, no database, stdlib-only Python.

autorunne

Repo-local project memory and handoff layer for direct AI coding agents, with validation evidence and sandbox-tolerant Autorunne state write-backs.

lerim

Compiles AI agent traces and truns them into reusable context.

memory-bank-skill

Universal long-term project memory for AI coding agents — Claude Code, Cursor, Windsurf, Cline + 4 more. TDD rules, code graph, spec-driven dev, cross-session recall.

ktw

The why layer of repo-native project memory: the reasoning behind a codebase as Markdown in the repo, versioned by Git, for coding agents and humans, so nothing rejected is proposed twice. No database, no daemon, no account.

ktw-lint

The why layer of repo-native project memory: the reasoning behind a codebase as Markdown in the repo, versioned by Git, for coding agents and humans, so nothing rejected is proposed twice. No database, no daemon, no account.

pyrecall-cli

Local project memory for Python — learn from corrections, recall conventions, pytest/typing/pathlib skills. CLI + stdio tool bridge. Zero network. MIT.

brain-ai-memory

Turn MEMORY.md into project-scoped, versioned memory for Codex, Claude Code, and MCP agents across sessions.

pmem-agent

Persistent, concurrent-safe project memory for Claude Code agents

keep-the-why

The why layer of repo-native project memory: the reasoning behind a codebase as Markdown in the repo, versioned by Git, for coding agents and humans, so nothing rejected is proposed twice. No database, no daemon, no account.