crispy-recall
Advanced tools
+1
-1
| { | ||
| "name": "crispy-recall", | ||
| "version": "0.1.4", | ||
| "version": "0.1.5", | ||
| "description": "Local session transcript memory for Claude Code and Codex — search past sessions with FTS5 + semantic vectors.", | ||
@@ -5,0 +5,0 @@ "license": "MIT", |
+31
-9
@@ -22,3 +22,3 @@ # crispy-recall | ||
| installs the `recall` skill. If Codex is detected it also gets the `recall` | ||
| skill (so the agent can search), but not an automatic per-turn hook in v0.1.0 — | ||
| skill (so the agent can search), but not an automatic per-turn hook (yet) — | ||
| index Codex history with `recall backfill --vendor codex`. After that, recall | ||
@@ -41,4 +41,4 @@ runs passively — you only invoke `recall` directly for `status`, `doctor`, | ||
| agent can search) and you can index your Codex history with | ||
| `recall backfill --vendor codex`. Real-time per-turn Codex indexing is **not** | ||
| in v0.1.0. | ||
| `recall backfill --vendor codex`. Real-time per-turn Codex indexing is **not | ||
| yet** supported. | ||
@@ -57,3 +57,3 @@ ## What it does | ||
| ```bash | ||
| $RECALL_BIN "the thing you're trying to remember" | ||
| recall "the thing you're trying to remember" | ||
| ``` | ||
@@ -64,8 +64,21 @@ | ||
| ```bash | ||
| $RECALL_BIN <session-id> <message-id> | ||
| recall <session-id> <message-id> | ||
| ``` | ||
| Search and list default to the **current directory's project** — from inside one | ||
| repo you only see that repo's sessions. Add `--all` to search across every | ||
| indexed project (use it for cross-repo questions, or when a scoped search comes | ||
| back thin), or `--project <path>` to target a specific repo regardless of where | ||
| you are: | ||
| ```bash | ||
| recall --all "the thing you're trying to remember" | ||
| ``` | ||
| The skill's frontmatter teaches Claude *when* to reach for this (before | ||
| non-trivial tasks, architectural decisions, or work with obvious prior | ||
| history), so in practice the agent calls it for you. | ||
| history), so in practice the agent calls it for you. (Inside the installed skill | ||
| the command is written out as `node ~/.recall/bin/recall.js` so it works even | ||
| when `recall` isn't on the agent's `PATH` — `$RECALL_BIN` in the skill source is | ||
| a placeholder the installer substitutes, not an environment variable you set.) | ||
@@ -76,2 +89,4 @@ ## Commands | ||
| |---|---| | ||
| | `recall "<query>" [--all] [--project <path>]` | Search past sessions (FTS5 + semantic). Defaults to the current project; `--all` searches every indexed project, `--project` targets one. | | ||
| | `recall <session-id> [<message-id>]` | Read a session, optionally centered on a matched message. | | ||
| | `recall install` | One-time setup: scaffold `~/.recall/`, wire the Stop hook, install the skill. | | ||
@@ -84,2 +99,7 @@ | `recall uninstall` | Reverse the install (skill, hook, CLAUDE.md block). `--purge` also removes `~/.recall/`. | | ||
| Add `--json` to `install`/`uninstall`/`status`/`doctor` for machine-readable | ||
| output. `recall install` also takes `--offline` (use a pre-staged binary + | ||
| model instead of downloading) and `--no-backfill` / `--auto-backfill` to control | ||
| the initial history index. Run `recall --help` for the full flag set. | ||
| ## Where things live | ||
@@ -95,5 +115,7 @@ | ||
| Everything is local. No telemetry, no network calls except the one-time | ||
| binary + model download at install. The DB is plain SQLite — open it with any | ||
| SQLite browser if you want to poke around. | ||
| Everything is local. No telemetry. The only data transfer is the one-time | ||
| binary + model download at install (from llama.cpp's GitHub releases and | ||
| HuggingFace); `recall install` and `recall doctor` also send lightweight | ||
| reachability probes to those two hosts. Nothing else leaves your machine. The DB | ||
| is plain SQLite — open it with any SQLite browser if you want to poke around. | ||
@@ -100,0 +122,0 @@ ## Troubleshooting |
Sorry, the diff of this file is too big to display
Sorry, the diff of this file is too big to display
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is too big to display
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
2396045
0.14%33085
0.06%128
20.75%