AnchorDB 1.0.6

Full Changelog: v1.0.5...v1.0.6

AnchorDB 1.0.5

Full Changelog: v1.0.4...v1.0.5

AnchorDB 1.0.4

Full Changelog: v1.0.3...v1.0.4

AnchorDB 1.0.3

Full Changelog: v1.0.2...v1.0.3

AnchorDB 1.0.2

Full Changelog: v1.0.1...v1.0.2

AnchorDB 1.0.1

Full Changelog: v1.0.0...v1.0.1

AnchorDB 1.0.0

Code memory for AI coding agents. Notes attached to files, spans, and symbols that stay attached as the code moves.

Install

go install github.com/jolovicdev/anchor-db/cmd/anchordb-mcp@v1.0.0
claude mcp add anchordb -- anchordb-mcp --db ~/.anchordb/anchor.db

Requires Go 1.25 or newer. See the README for the CLI, HTTP API, and web viewer.

What it does

Chat history is a bad place to keep what you learn about a codebase. It scrolls away, it is not attached to anything, and the next session starts blank. AnchorDB keeps those notes beside the code and follows the code when it moves.

Git-aware relocation. Anchors record the commit their line numbers came from, so resolution maps old lines to new through git diff before falling back to text matching. A span that only moved is found exactly rather than guessed at from surrounding text — which matters when the same code appears more than once in a file. The mapping is verified against the stored text before it is applied.

Stale triage. An anchor that cannot be placed is marked stale with a reason that distinguishes rewritten code from deleted code, and offered ranked relocation candidates with previews. Accept one over HTTP, the CLI, MCP, or in the viewer.

History. Every move, stale, and update is recorded with its reason and confidence, readable from all four surfaces.

Four surfaces, one SQLite file. An MCP server for coding agents, an HTTP API and web viewer for humans, and a CLI for scripts and CI.

Symbol support

Go, Python, JavaScript, and TypeScript via tree-sitter. Files in other languages work too, resolved by span and text rather than by symbol.