linksee-memory 0.0.7 → 0.0.9

package/README.md

@@ -191,6 +191,95 @@ Aggregated MCP-usage data helps the [KanseiLink](https://kansei-link.com) projec
 
 The full payload schema and validation logic is open-source — read `src/lib/telemetry.ts` if you want to verify exactly what leaves your machine.
 
+## Pricing
+
+**Free forever.**
+
+linksee-memory is local-first and runs entirely on your machine. There is no hosted component you need to pay for. The SQLite DB lives in your home directory; backup = file copy.
+
+No account, no credit card, no API key. Just install and use.
+
+## Troubleshooting
+
+<details>
+<summary><b>The skill isn't firing — Claude Code doesn't call <code>recall</code> when I ask about past work.</b></summary>
+
+1. Verify the skill was installed:
+   ```bash
+   ls ~/.claude/skills/linksee-memory/SKILL.md
+   ```
+   If absent, run `npx -y linksee-memory-install-skill`.
+2. Restart Claude Code. Skills are indexed on session start.
+3. Check that the MCP is registered under the name `linksee` (the skill expects `mcp__linksee__*` tool names):
+   ```bash
+   claude mcp list | grep linksee
+   ```
+   If it's registered as something else, either re-register or edit `~/.claude/skills/linksee-memory/SKILL.md` to match.
+</details>
+
+<details>
+<summary><b>Stop hook isn't recording my sessions.</b></summary>
+
+1. Check the hook log: `cat ~/.linksee-memory/hook.log`
+2. Run a manual test:
+   ```bash
+   echo '{"session_id":"test","transcript_path":"/path/to/some.jsonl"}' | npx linksee-memory-sync
+   ```
+3. Make sure the `Stop` hook in `~/.claude/settings.json` points to `npx -y linksee-memory-sync` (not the old `-import`).
+</details>
+
+<details>
+<summary><b>Upgrading from v0.0.5 or earlier — my recalls are mostly tagged "Card_Navi" or my project-dir name.</b></summary>
+
+v0.0.6+ fixed the entity detection bug that collapsed all memories into the session's starting cwd. To re-index existing history with correct project attribution, run:
+
+```bash
+npx linksee-memory-import --all
+```
+
+The importer is idempotent (wipes existing session data before re-inserting). Typical runtime: a few minutes for hundreds of sessions. Expect a dramatic improvement in `recall` precision afterward.
+</details>
+
+<details>
+<summary><b><code>recall</code> returns too much — the context window fills up fast.</b></summary>
+
+Reduce `max_tokens`:
+```
+recall({ query: "...", max_tokens: 800 })   // default is 2000
+```
+Or narrow with `entity_name` and `layer`:
+```
+recall({ query: "...", entity_name: "my-project", layer: "caveat" })
+```
+</details>
+
+<details>
+<summary><b>How do I reset / delete all memory?</b></summary>
+
+```bash
+rm -rf ~/.linksee-memory   # nuke everything; next run creates a fresh DB
+```
+
+Or delete individual memories via the `forget` tool with a specific `memory_id`.
+</details>
+
+<details>
+<summary><b>DB is getting large (>100 MB). How do I trim it?</b></summary>
+
+Run consolidate — it clusters old cold memories into compressed learning-layer summaries:
+```
+consolidate({ scope: "all", min_age_days: 7 })
+```
+Caveat and active-goal layers are always preserved. Consider scheduling a weekly run via cron / Task Scheduler.
+</details>
+
+## Support
+
+- **Issues & bug reports**: [github.com/michielinksee/linksee-memory/issues](https://github.com/michielinksee/linksee-memory/issues)
+- **Feature requests**: open an issue with the `enhancement` label
+- **Security concerns**: see [SECURITY.md](./SECURITY.md) if present, or file a private advisory on GitHub
+- **Company**: Synapse Arrows PTE. LTD. (Singapore)
+
 ## License
 
 MIT — Synapse Arrows PTE. LTD.

package/dist/lib/session-extractor.js

@@ -31,9 +31,29 @@ const FAILURE_PATTERNS = [
     /失敗|バグ|エラー|直して|修正|戻して/,
     /error|bug|fail|broken|revert|rollback/i,
 ];
+// Caveats must be EXPLICIT warnings/prohibitions the user wants preserved.
+// Previous bare patterns (/注意/ /やらない/ /避けて/) caught descriptive usage
+// like「一般ユーザーはやらない」「Anthropicがやらない範囲」and turned
+// opinions into protected caveats. Tightened to imperative/prohibitive forms
+// only. Loses some recall, but precision matters more for the "never forget"
+// layer.
+// Imperative negations: `[ぁ-ん一-龯]ないで` reads as "don't do X" only when
+// what follows is NOT part of a polite negation (「ないです」 = "it is not"),
+// a probability form (「ないでしょう」), a request (「ないでほしい」), or a
+// continuation (「ないでいる」). The negative lookahead `(?![すしいほ])`
+// catches all four cases in one filter (す: です, し: しょう, い: いる/いない,
+// ほ: ほしい). 「ないでください」 still passes because "く" is not excluded.
 const CAVEAT_PATTERNS = [
-    /注意|気をつけ|避けて|やらない|禁止/,
-    /do not|never|avoid|watch out/i,
+    // `ダメだ(?!った|ろうと|と思)` excludes 過去形 (ダメだった = "it failed") and
+    // speculation (ダメだろうと) which are descriptive, not prescriptive.
+    // `ないで` only counts as imperative when it ends the clause. We accept:
+    //   sentence terminators 。！!、 / particles ね・よ / whitespace / ください
+    // Anything else (e.g. も = concessive「〜ないでも」, 止まる・いる・ほしい etc.)
+    // is treated as descriptive and excluded.
+    /気をつけて|注意して|[！!]注意[！!]|避けて(?!いる|いない)|[ぁ-ん一-龯]ないで(?=[。！!、\s]|ください|ね[^い]|よ[^う]|$)|やめて(?!おく|ほし)|禁止|ダメだ(?!った|ろうと|と思)|危険[だです]/,
+    // English: require a concrete action after avoid/don't/never — a bare
+    // "Avoiding rebuild of unchanged files" in a Vercel log is not a caveat.
+    /\b(?:don'?t|do\s+not)\s+(?:do|use|run|call|forget|try|send|share|commit|push|paste|edit)\b|\bnever\s+(?:do|use|call|share|commit|paste|run|push|edit)\b|\bavoid\s+(?:using|running|calling|committing|pushing|sharing|pasting|editing|creating|modifying)\b|\bwatch\s+out\b/i,
 ];
 function matchesAny(text, patterns) {
     return patterns.some((p) => p.test(text));

package/dist/lib/session-parser.js

@@ -118,6 +118,17 @@ export function isPastedExternalContent(text) {
     // Service status pages / logs
     if (/^(Service offline|Failed|Success|Deployment|Build|Logs?|Error:)/.test(t.slice(0, 80)))
         return true;
+    // CI/CD and cloud build logs are almost always pasted and contain substrings
+    // (Avoiding / Running / never / error) that false-trigger the caveat patterns.
+    // Detect by timestamp-prefixed first line (e.g. "17:40:13.469 Running build")
+    // or by dense occurrence of ISO-time prefixes.
+    if (/^\d{1,2}:\d{2}:\d{2}[.:]\d{2,3}\s/.test(t))
+        return true;
+    if ((t.match(/\d{1,2}:\d{2}:\d{2}[.:]\d{2,3}/g) || []).length >= 3)
+        return true;
+    // Deployment-success notice from Vercel / Netlify / etc. (pasted by user)
+    if (/^成功しました/.test(t) && /デプロイ|deploy/i.test(t.slice(0, 200)))
+        return true;
     // Extractor-internal duplicate (was generating same caveat per session)
     if (t === 'Review errors before repeating this workflow.')
         return true;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "linksee-memory",
-  "version": "0.0.7",
+  "version": "0.0.9",
   "mcpName": "io.github.michielinksee/linksee-memory",
   "description": "Local-first agent memory MCP — cross-agent brain with 6-layer structured memory + token-saving file diff cache",
   "type": "module",