chat-recall 0.6.1 → 0.6.4

package/README.md

@@ -12,29 +12,40 @@
 
 **[chatrecall.dev](https://chatrecall.dev)** · [How it works](https://chatrecall.dev/how-it-works/) · [MCP tools](https://chatrecall.dev/mcp/) · [Pricing](https://chatrecall.dev/pricing/) · [Self-host](https://chatrecall.dev/self-hosting/) · [Security](https://chatrecall.dev/security/)
 
-> Memory, secret scanning and code findings across every AI coding tool you use. They all share a single searchable history — and the agent works it itself.
+> Turn what your AI coding tools already write into shared team knowledge, leaked-secret alerts, ranked code findings and tracked tasks.
 
-Your coding agents each keep their own transcripts, in their own format, in their own directory, and none of them can read another's. `chat-recall` indexes all of them into one place, redacts secrets on the way, and exposes the result to your agent through **61 MCP tools**.
+**Your agents wrote it all down. Nobody read it.**
 
-Memory is the foundation, not the whole product. One index, read three ways:
+Every coding agent you run keeps a full transcript of its work: the decisions, the
+reasoning, the keys somebody pasted, the problems it found and never filed. Each one
+writes to its own directory in its own format, none can read another's, and nothing
+reads any of them. `chat-recall` does, through **61 MCP tools**.
 
 | | What it does | Tools |
 |---|---|---|
-| **Recall** | Resume a session, search what you actually typed, read the diffs and commits it produced, recall a decision and why it was made | 37 |
-| **Security** | Flag credentials pasted into past conversations, per session, and track each one until it is rotated or dismissed | 4 |
-| **Code findings** | Rank what is worth fixing in a project and turn it into actionable tasks, with code intelligence over the repo itself | 12 |
+| **Shared AI knowledge** | Decisions, conventions and project facts one agent learned, available to every other agent and every teammate. Time-aware, so a superseded decision reads as superseded | 16 |
+| **Security findings** | Credentials pasted into past conversations, flagged per session, checked for whether they still work, and tracked until rotated or dismissed | 4 |
+| **Automated code improvements** | Ranks what is actually worth fixing in a repository, then applies or dismisses each recommendation, with code intelligence over the repo itself | 9 |
+| **Task tracking** | A shared board fed by those findings, with rules per repository, so a finding becomes work instead of a report | 5 |
 
-That cross-tool part is the point. A single tool's built-in history stops at its own boundary; this does not.
+Underneath all four is one index of every session your tools already wrote, and 28
+more tools to search, replay and diff it. That index is the mechanism. It is not
+the pitch, and it is not why anyone buys this.
+
+The cross-tool part is what makes it work. A single tool's built-in history stops at
+its own boundary. This does not, and neither does your team.
 
 ## See it work
 
-Every screen below is a real MCP call against a real server — the exact tool and
-arguments are shown above each response. Nothing is mocked, replayed or re-timed.
+Every screen below is real output against a real server, captured from the demo
+account. Nothing is mocked, replayed or re-timed.
 
-**One memory, every tool.** Here **OpenCode** is asked about a **Claude Code**
-session: a different tool, a different transcript format, one index.
+**One index, every tool.** Search finds a session by what was *discussed* in it,
+not by its filename, and `memory status` shows every source type in one place —
+sessions beside the skills, MCPs, commands, subagents and hooks that produced
+them.
 
-![recall_smart_resume called from OpenCode with a Claude Code session id, returning that session's request, plan and completed work](docs/media/7-cross-claude.png)
+![chat-recall search finding a past session by what was discussed in it, and memory status listing every indexed source type](docs/media/7-cross-claude.png)
 
 **Or just ask in plain English** — no tool names, no session ids. The agent picks
 the call itself:
@@ -58,7 +69,6 @@ That indexes the transcripts already on your disk, detects which AI tools you ha
 |---|---|
 | Claude Code | `~/.mcp.json` |
 | Codex | `~/.codex/config.toml` |
-| Gemini CLI | `~/.gemini/settings.json` |
 | OpenCode | `~/.config/opencode/opencode.json` |
 | Cursor | `~/.cursor/mcp.json` |
 
@@ -120,7 +130,7 @@ Exclusions live on the machine that holds the data, so the CLI owns them; they a
 
 ## Four things it actually does
 
-1. **Cross-tool unified memory.** One index, one search, one UI over Claude Code (`~/.claude/projects/`), Gemini CLI (`~/.gemini/tmp/`), Codex (`~/.codex/`), OpenCode (`~/.local/share/opencode/`), Antigravity and Cursor (`~/.cursor/` for the CLI, `~/.config/Cursor/` for the IDE). Sessions, plans, tasks, CLAUDE.md files, paste cache, shell history and agent diaries all share one pluggable `MemorySource` interface.
+1. **Cross-tool unified memory.** One index, one search, one UI over Claude Code (`~/.claude/projects/`), Codex (`~/.codex/`), OpenCode (`~/.local/share/opencode/`), Antigravity (`~/.gemini/antigravity-cli/`) and Cursor (`~/.cursor/` for the CLI, `~/.config/Cursor/` for the IDE). Sessions, plans, tasks, CLAUDE.md files, paste cache, shell history and agent diaries all share one pluggable `MemorySource` interface.
 2. **The agent recalls itself.** 61 MCP tools, so Claude Code can `recall_smart_resume`, `recall_search` (with `like_session` to find similar work), `recall_edits_timeline`, `recall_subagent_search` and `recall_redundant_files` rather than asking you what happened last time. It writes back too, via `recall_decision_record`, `recall_kg_add` and `recall_set`.
 3. **Warns before you redo work.** A `UserPromptSubmit` hook searches for similar past sessions on every prompt and injects a short "you have done this before, in session X" note into the agent's context.
 4. **Temporal knowledge graph.** Decisions and tool mentions become entity-relationship triples with `valid_from`/`valid_to` windows, so you can ask what was decided in March and whether it still holds.
@@ -251,7 +261,6 @@ codeindex is open source (MIT) at [github.com/munhq/codeindex](https://github.co
 | Source | Origin | Notes |
 |--------|--------|-------|
 | **Sessions (Claude)** | `~/.claude/projects/<hash>/<uuid>.jsonl` | Full transcripts, tokens, cost, files touched, models used |
-| **Sessions (Gemini CLI)** | `~/.gemini/tmp/*/chats/*.json` | Tokens and tool usage extracted where present |
 | **Sessions (OpenCode)** | `~/.local/share/opencode/opencode.db` (SQLite) | Cost, tokens, todos |
 | **Subagent transcripts** | `<session-dir>/<id>/subagents/*.jsonl` | Explore, aside, **and `acompact-*`** (orphaned compacted history) |
 | **Plans** | `~/.claude/plans/*.md` | Agent planning docs, split by `##` |
@@ -328,7 +337,7 @@ No telemetry. Your data lives in **your** server's Postgres — back that up how
 packages/
 ├── engine/src/
 │   ├── core/
-│   │   ├── backends/        ToolBackend per AI tool (claude, gemini, opencode, codex, agy)
+│   │   ├── backends/        ToolBackend per AI tool (claude, opencode, codex, agy, cursor)
 │   │   ├── tool-backend.ts  Registry interface — single source of truth for tool identity
 │   │   ├── tool-paths.ts    Env-overridable default paths for each tool
 │   │   ├── generic-engine.ts  Shared turn extraction / edit scan / replay (canonical events)
@@ -351,13 +360,13 @@ e2e/                     Playwright tests for the dashboard
 Two extension points, both registry-driven:
 
 - **Adding a new content type** (e.g. another file format to index) — implement `MemorySource` (`discover` → `parse` → `extractLinks`) and register it in the `SourceRegistry`.
-- **Adding a new AI tool** (a seventh backend alongside Claude/Gemini/OpenCode/Codex/Antigravity/Cursor) — implement `ToolBackend` (paths, ID handling, `readEvents`, `fileToolMap`, `extractEditDelta`) and register it in `packages/engine/src/core/backends/index.ts`. All paths are env-overridable via `CHAT_RECALL_{CLAUDE,GEMINI,CODEX,AGY,CURSOR,CURSOR_IDE}_HOME` / `CHAT_RECALL_OPENCODE_DB`.
+- **Adding a new AI tool** (a sixth backend alongside Claude/OpenCode/Codex/Antigravity/Cursor) — implement `ToolBackend` (paths, ID handling, `readEvents`, `fileToolMap`, `extractEditDelta`) and register it in `packages/engine/src/core/backends/index.ts`. All paths are env-overridable via `CHAT_RECALL_{CLAUDE,CODEX,AGY,CURSOR,CURSOR_IDE}_HOME` / `CHAT_RECALL_OPENCODE_DB`.
 
 ## Requirements
 
 - Node.js 22 or later. The Docker image and CI run 24.
 - Sessions written by a supported tool, in its standard location: `~/.claude/`,
-  `~/.codex/`, `~/.local/share/opencode/`, `~/.gemini/`.
+  `~/.codex/`, `~/.local/share/opencode/`, `~/.gemini/antigravity-cli/`.
 
 That is the whole list. No API key is needed to install, index or search.