Main
Install the daemon + wrapper first, then install hooks; without hooks you get read access but not ambient capture/recall.
Treat
iai-mcp doctor+daemon statusas your safety gates before enabling it in a real project session.If you care about numbers, run the repo’s benchmark modules to measure recall latency and fidelity on your machine.
Source-backed notes
- README Install section uses
bash scripts/install.shand documents adding~/.local/binto PATH foriai-mcp. - README documents capture/recall hooks (
iai-mcp capture-hooks install|status|uninstall) and shows a Codex target option. - README includes benchmark claims (e.g., p95 <100ms, >=99% verbatim recall at 10k) and points to
bench/modules.
FAQ
- Is it cross-platform?: README lists macOS as supported and calls out Windows/Linux as not supported yet.
- Does it store secrets?: It stores your captured transcript locally; treat the store directory like any sensitive developer artifact.
- What if the daemon is down?: README describes hooks as fail-safe; session start should not block if recall returns empty.