<p align="center"> <img src="assets/banner.png" alt="engram — AI coding memory" width="100%"> </p> <p align="center"> <a href="#install"><strong>Install</strong></a> · <a href="#usage"><strong>Usage</strong></a> · <a href="#mcp-server"><strong>MCP Server</strong></a> · <a href="#how-it-works"><strong>How It Works</strong></a> · <a href="docs/INTEGRATION.md"><strong>Integration Guide</strong></a> · <a href="#contributing"><strong>Contributing</strong></a> </p> <p align="center"> <a href="https://github.com/NickCirv/engram/actions"><img src="https://github.com/NickCirv/engram/actions/workflows/ci.yml/badge.svg" alt="CI"></a> <img src="https://img.shields.io/badge/license-Apache%202.0-blue" alt="License"> <img src="https://img.shields.io/badge/node-%3E%3D20-brightgreen" alt="Node"> <img src="https://img.shields.io/badge/tests-520%20passing-brightgreen" alt="Tests"> <img src="https://img.shields.io/badge/LLM%20cost-$0-green" alt="Zero LLM cost"> <img src="https://img.shields.io/badge/native%20deps-zero-green" alt="Zero native deps"> <img src="https://img.shields.io/badge/token%20savings-up%20to%2090%25-orange" alt="Up to 90% token savings"> </p>

---

The context spine for AI coding agents.

One call replaces five. engram intercepts file reads and serves rich context packets — structural summaries, decisions, library docs, known issues, and git history — assembled from 6 providers in a single ~500-token response. Your AI agent gets everything it needs without making 5 separate tool calls.

engram installs a hook layer at the Claude Code tool-call boundary. Every Read, Edit, Write, and Bash cat gets intercepted. When the graph has confident coverage of a file, it serves a rich context packet combining structure, decisions, docs, and history — all pre-assembled, all within budget.

Not a memory tool. Not a RAG layer. **The context spine that connects your knowledge graph, semantic memory, library docs, and project notes into