Talamus
Local-first, source-grounded memory for AI agents, with citations, bitemporal history, review-gated corrections, and MCP tools for search and recall.
README
Talamus
<!-- mcp-name: io.github.ampres-ai/talamus -->
Your AI agent forgets why a decision was made as soon as the session ends.
Talamus turns agent sessions, documents, notes, repos, and URLs into local, source-grounded Markdown memory that the next session can search and cite.
Markdown stays the source of truth. Search and graph stay on your machine. No hosted account or required embeddings.
Try the whole local retrieval loop first — no setup, account, LLM, or hook:
pipx install "talamus[mcp]"
talamus demo
talamus search "embedding"
talamus read "Embedding"
If local, inspectable agent memory should stay discoverable, click Star at the top of this page. It is the clearest signal that Talamus is worth maintaining in public.

Talamus is an open-source project by Ampres, an independent AI and open-source lab.
Connect an agent in 60 seconds
Copy-pasteable arc, with the reproducible version in scripts/demo/run_magic.py:
-
Set up the project brain.
talamus setupinitializes the brain, chooses an engine, installs MCP for Claude Code, Cursor, Codex, OpenCode, and OpenClaw when detected, asks once before installing the session-capture hook, and can probe the engine with one tiny live call.talamus setup -
Your agent session ends. The consented hook reads the transcript and git diff, applies the worth-remembering gate, writes only useful memory into this brain, and audits the event at
.talamus/logs/capture.log. -
A fresh session asks what happened and gets an answer from real notes, with sources.
talamus recall "why did we choose FTS5?" talamus ask "why did we choose FTS5?" -
Reproduce the scripted demo without spending LLM calls, or run it with your real engine.
python scripts/demo/run_magic.py --fake python scripts/demo/run_magic.py --keep --engine claude-cli
What is different
TIME: notes have version history, facts have valid-time windows, and talamus ask --as-of 2026-01 answers from the brain as it was.
MEANING: the ontology is induced from evidence, versioned, promoted by measured rules, and used to cluster and route the brain.
VERIFIABILITY: every note carries provenance; talamus verify proposes corrections to review, and answers cite the notes they used.
Measured comparison
The one-screen benchmark is rendered at docs/benchmarks.md and committed at benchmarks/results/one-screen.md. Every number below traces to a committed artifact under benchmarks/results/.
| corpus | metric | Talamus | BM25 | MiniLM vector DB |
|---|---|---|---|---|
| SciFact, English-only turf | recall@10 | 0.797 | 0.776 | 0.783 |
| SciFact, English-only turf | nDCG | 0.664 | 0.652 | 0.645 |
| Book, cross-language + vague | hit@10 | 0.971 | 0.829 | 0.743 |
| Book, cross-language + vague | recall@10 | 0.929 | 0.771 | 0.700 |
Also measured in committed artifacts: −97.7% tokens per answer versus loading the brain into context, refusal 1.000 on out-of-scope questions, and search latency p95 72.6 ms at 10k notes / p50 624 ms at 100k.
The honest part: retrieval quality tracks the LLM you bring. With a strong expansion engine, talamus-smart leads a strong multilingual dense model (multilingual-e5) on every metric including ranking (nDCG 0.847 vs 0.837); with a weak or free one, e5 leads ranking while Talamus keeps the best hit/recall — and on a slow local engine, plain search beats --smart outright. Every number traces to a committed artifact; the losses stay on the table.
Engines
Bring the LLM you already have: claude-cli, codex-cli, antigravity-cli (agy), opencode, ollama, or anthropic-api.
Quickstart
pipx install "talamus[mcp]"
talamus setup
talamus ingest ./notes && talamus ask "what should I remember?"
Run talamus for the status dashboard, talamus quickstart for essential commands, or talamus ui for the local React workbench.
Install the consent-aware Talamus agent skill from skills.sh:
npx skills add ampres-ai/talamus --skill talamus-memory
OpenClaw can install the same standalone skill directly from ClawHub:
openclaw skills install @ampres-ai/talamus-memory
Installing the standalone skill does not install Talamus automatically. If the CLI is missing, the skill explains the isolated installation choices and asks before running one.
Gemini CLI can install Talamus directly from its extension gallery or from this
repository. The extension starts the pinned PyPI release through uvx, so it
does not modify the cloned source tree:
gemini extensions install https://github.com/ampres-ai/talamus --auto-update
goose can install the repository as an Open Plugin. This adds the consent-aware memory skill and starts the pinned local MCP server for each new CLI session:
goose plugin install https://github.com/ampres-ai/talamus.git
The plugin requires uv on PATH; uvx downloads Talamus and its MCP
dependencies into an isolated cache on first use.
Containerized MCP (the brain remains in the mounted local folder):
docker run --rm -i -v "$PWD:/data" ghcr.io/ampres-ai/talamus:1.1.0
Links
Docs: quickstart, local-first agent memory, agent install guide, commands, agent tool calling, configuration, benchmarks, architecture, design principles, evaluation, multi-brain, ontology.
Project: security, contributing, roadmap, changelog.
Maintained by Ampres. Source code and issue tracking live at ampres-ai/talamus.
Development
pip install -e ".[dev,mcp]"
python dev.py
python dev.py runs ruff, format check, mypy, and unittest. Product behavior changes should update user docs in the same change.
License
Apache-2.0.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.