Get This Tool
Callimachus
Pricing
- Model
- Free
Summary
You fixed that obscure Rust borrow-checker issue three weeks ago in a Claude Code session — then opened Cursor the next day and started from scratch because you couldn't find the thread. Callimachus is the local index that makes that problem stop happening.
The vendor describes Callimachus as a background watcher that indexes conversation history from eleven AI coding tools — Claude Code, Cursor, Cline, Codex, and seven others — into a single on-device catalogue with both keyword and semantic search. You query it from a desktop app, a VS Code sidebar, the terminal, or an MCP server that lets other agents pull your past threads directly. The index never leaves your machine: no account, no telemetry, AGPL-3.0 source available. The distillation features — summarizing decisions and gotchas across threads — require either a local Ollama setup or a cloud API key, so that layer is not zero-dependency. Teams running agents that aren't on the eleven supported list get no indexing without manual workarounds.
Bottom line: Pick this if you context-switch between multiple AI coding tools daily and keep re-explaining solved problems to each one — but if your workflow centers on a tool outside the eleven supported, you're cataloguing a partial history.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Hybrid keyword-plus-semantic search over local conversation history, so a half-remembered description of a fix surfaces the right thread without knowing the exact words you used the first time.
- Indexes eleven AI coding tools into one catalogue, which means you stop re-explaining context to each tool independently after switching environments mid-task.
- Fully local operation — index, embeddings, and search all stay on disk with no account or telemetry — so conversations with proprietary codebases never leave the machine, which matters for any team under an NDA or SOC 2 obligation.
- MCP server exposes indexed history to other agents on demand, so an agent starting a new session can retrieve your prior decision on the same problem rather than rediscovering it from scratch.
- AGPL-3.0 source means you can audit exactly what the indexer reads and stores — you don't have to accept the vendor's privacy statement on faith.
Cons
Sign in to edit- The distillation and cited-answer features require either a local Ollama install or a cloud API key — teams expecting a fully zero-dependency local experience hit this wall the first time they try to summarize decisions across threads and find that feature is not bundled.
- Support is limited to eleven specific tools at v0.6.1; a team whose primary coding agent is outside that list gets no automatic indexing, and the vendor page describes no generic import format, so that history stays invisible to the catalogue.
- There is no Windows or Linux desktop auto-update infrastructure described beyond 'auto-updates' for macOS — teams on Linux running the CLI or MCP surface manage updates manually, which adds friction in production environments with multiple machines.
- A team that needs indexed history shared across multiple developers — not just one local machine — will find no sync or multi-user path here; at that point they are looking at self-hosted vector search infrastructure or a different tool entirely.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- macOS, Windows, Linux
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-06-22T10:22:45.808Z
Best For
Who it's for
- Developers who switch between multiple AI coding tools
- Users needing offline access to their full conversation history
- Teams or individuals who want cited answers over personal logs
What it does well
- Locate a specific past debugging thread across multiple agents
- Retrieve code snippets or decisions from prior sessions by semantic query
- Export conversation context into an editor or Obsidian
- Feed indexed history to other agents via MCP server
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is Callimachus free?
- Yes — Callimachus is fully free to use. There is no paid tier.
- Is Callimachus open source?
- Yes. Callimachus is open source.
- Can I self-host Callimachus?
- Yes. Callimachus supports self-hosting on your own infrastructure.
- What platforms does Callimachus support?
- Callimachus is available on: macOS, Windows, Linux.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Every AI coding session solves something. Almost none of that solution survives into the next session, because there’s no index — just a flat list of threads scattered across five tools and three weeks. Callimachus runs quietly in the background and indexes those conversations as they’re written, building a local SQLite + on-device embedding index that you can query by keyword, by meaning, by file path, by project, or by recency. The result is a searchable catalogue of your own debugging history, not a cloud sync or another SaaS subscription.
The differentiating layer is hybrid search: SQLite FTS5 keyword matching fused with on-device semantic similarity. The docs describe this as letting a vague memory — ‘that vector index migration’ — surface the correct thread even when the exact words are gone. Subagent transcripts are indexed separately and stay collapsed until you ask for them. A ‘cited answer’ feature runs retrieval-augmented generation over your own session history, returning a synthesized response with [thread N] citations back to the source threads — though this requires an LLM engine, either local Ollama or a cloud API key.
Callimachus exposes the same index through four surfaces: a native desktop app for macOS, Windows, and Linux; a VS Code and Cursor sidebar extension; a `cal` CLI for terminal-based search and piping context into other tools; and an MCP server that lets any MCP-compatible agent query your history on demand. The MCP path is the sharpest edge for teams already running agent workflows — an agent can pull your past decisions rather than starting cold. The hard constraint is the supported tool list: eleven tools are indexed at v0.6.1. If your team’s primary tool is not on that list, no indexing occurs without a manual import path the vendor page does not describe.