STiFLeR7/memex

> Keeps your AI coding agents' engineering context current as the code changes.
> memex builds a bitemporal knowledge graph of your repository (modules,
> symbols, decisions, problems, evidence, and code evolution). In v1 it also
> hooks into Claude Code and Codex: each session starts with the right context,
> each edit is checked against the current code, and the agent is told exactly
> what changed.
**memex.stifler.in**
A daemon, hook service and MCP server that turn commits and file changes into
structured engineering knowledge and deliver it to agents with freshness and
provenance preserved, without making memex a source of personal memory or raw
session state.
Where memex lives
| | |
|---|---|
| Website | memex.stifler.in |
| Source | github.com/STiFLeR7/memex |
| Python package | memex-mcp on PyPI |
| Node package | stifler-memex-mcp on npm |
| MCP Registry | registry.modelcontextprotocol.io, listed as io.github.STiFLeR7/memex |
| Claude Code plugin | STiFLeR7/claude-plugins |
| Directories | Glama · AI Agents Listing |
Evaluation record in BENCHMARK.md, release history in
CHANGELOG.md, reporting process in SECURITY.md,
and how to work on it in CONTRIBUTING.md.
https://github.com/user-attachments/assets/b14e3185-ea36-4ae5-bd18-2d34e6bf7be4
*memex v1 in 60 seconds. If the player does not load, download the video.*
Live context (v1)
Coding agents work from a snapshot of the code. A teammate pushes, another
agent edits a file, a branch moves, and the agent keeps acting on what it read
earlier. v1 keeps that snapshot current, inside Claude Code and Codex:
| When | What memex does |
|---|---|
| **Session start** | Delivers a bounded working set for the task, and confirms delivery from the client's own session record |
| **Before each edit** | Checks whether the context the edit rests on still holds. If not, the edit is held, the agent gets a scoped correction, and it revises |
| **On resume** | If the code changed while the session was away, names the files to re-read |
| **Parallel agents** | Gives each linked worktree its own view, so agents side by side each see their own code |
| **Trying it out** | memex v1 mode shadow records what would be corrected without changing anything; hooks fail open; memex v1 rollback stops memex at once |
memex needs a Neo4j 5 server you already run (Docker is not required). Hooks go
only into the checkout's own project configuration, and memex never asks for or
stores your client credentials. Full guide, host recipes and rollback:
docs/v1/25_ONBOARDING.md.
Install
Via Claude Code marketplace
Restart your Claude Code session.
The first start after installing or upgrading downloads memex's Python
dependencies (about 40 seconds), which can exceed Claude Code's MCP connect
timeout once. Warm it up first, then restart:
If Claude Code still shows a connection timeout, open /mcp and reconnect
memex. If a tool says memex cannot reach Neo4j, start Neo4j (for example
docker start memex-neo4j); the tools recover without a restart.
Manual
bash
bash docker/bootstrap-team-env.sh
docker compose -f docker/docker-compose.team.yml up -d
mermaid
flowchart TD
Init[memex init extract baseline] --> Watch[memex watch daemon + git hooks]
Watch -->|commit| Extract[tree-sitter extract symbols, imports, lockfile]
Extract --> Synth[Gemini Flash diff → Decision nodes]
Synth --> Write[Graphiti add_episode + post-hoc bitemporal SET]
Write --> Decay[Scheduler nightly confidence decay]
Decay -->|stale edges| Archive[expired_at = now]
Serve[memex serve MCP stdio/HTTP] -.->|reads| Write
Agent[AI agent] -->|14 MCP tools| Serve