memex-mvp 0.10.6 → 0.10.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memex-mvp",
-  "version": "0.10.6",
+  "version": "0.10.7",
   "description": "Local-first MCP server for cross-agent AI memory. One SQLite + FTS5 corpus across Claude Code, Cowork, Cursor, Continue, Zed, Obsidian, and Telegram — passively captured, verbatim, searchable from any MCP-compatible client.",
   "type": "module",
   "main": "server.js",

package/server.js

@@ -874,14 +874,46 @@ without context the user spent months building is much larger.
 
 ══ FIRST CONTACT IN A SESSION ══
 
-ON YOUR FIRST MEMEX CALL IN A NEW SESSION, START WITH memex_overview.
-It returns a single-page snapshot — sources breakdown, totals, date
-range, the 10 most recent conversation titles, AND the live status of
-the auto-capture daemon. This gives you a mental map of what is and
-is not in memory, so subsequent searches are sharper than blind
-guessing. One overview call costs ~500 tokens and saves many wasted
-memex_search attempts. Skip it only if the user explicitly named a
-conversation_id you can fetch directly.
+ON YOUR VERY FIRST INTERACTION IN A NEW SESSION — BEFORE responding
+to the user's first message — CALL memex_overview. This is not
+optional. It is your equivalent of a SessionStart hook for clients
+that don't have one (Cursor, Cline, Continue, Zed, Claude Desktop —
+i.e. everyone except Claude Code CLI).
+
+Why this first, automatically:
+
+  1. memex_overview returns the corpus snapshot in one call (~500
+     tokens) — sources, counts, date range, 10 most recent
+     conversation titles, AND the live status of the auto-capture
+     daemon. You build a mental map; subsequent memex_search queries
+     are sharper than blind guesses.
+
+  2. The response includes a telegram_pending field — a list of
+     Telegram exports the user has staged but not yet imported. If
+     count > 0, MENTION THIS to the user PROACTIVELY in your first
+     reply, before answering whatever they asked. Example:
+       "Before I help with X — I noticed you have 3 Telegram chats
+        ready to import to memex (Family, Work team, Mom). Want me
+        to handle that now? Or remember it for later?"
+     Then call memex_telegram_pending for the full list when they
+     say yes, and memex_telegram_import for the selected chats.
+
+  3. The response includes a sync-status banner. If the daemon is
+     down (🔴) or not installed (⚪), surface this too — the user
+     may not realize their memory has stopped capturing.
+
+When to SKIP memex_overview on first contact:
+  • The user explicitly named a conversation_id — fetch directly
+  • The conversation is clearly not memory-related (e.g. user asked
+    you to debug their code in a non-memex repo, no recall implied)
+  • You're already running INSIDE Claude Code CLI AND its SessionStart
+    hook has already injected memex context (you'll see "memex auto-
+    context for ..." in your system message). In that case the hook
+    did this work — don't double-call.
+
+Otherwise: call memex_overview first. Always. The cost is small; the
+benefit (proactive Brian Chesky moment for Telegram imports + map of
+the corpus) is large.
 
 ══ AUTO-CAPTURE DAEMON (memex-sync) ══
 

package/skills/install-memex/README.md

@@ -47,21 +47,25 @@ The skill description is written so Claude / OpenClaw auto-invoke it from any ph
 
 > **User:** install memex
 >
-> **Agent:** 👋 You're running inside Cursor. Let me run a quick discovery before any install actions...
+> **Agent:** 👋 You're running inside Cursor. Quick discovery before any install actions...
 >
 > ✓ Found Claude Code data at `~/.claude/projects/` (8 sessions)
-> ✓ Found Cowork sessions (3 subagent transcripts in your projects)
+> ✓ Found Cowork sessions (3 subagent transcripts)
 > ✗ Continue not installed
 > ✗ Zed not installed
 > ✓ Cursor data found (this is where I'll write the MCP config)
 >
-> After install, memex will auto-index conversations from: Claude Code, Cowork, Cursor. Drop Telegram exports into `~/.memex/inbox/` manually if you want those too.
+> After install, memex will auto-index conversations from: **Claude Code, Cowork, Cursor**. v0.10+ also auto-detects Telegram Desktop exports — when you export a chat, memex stages it and I'll ask which to import (privacy-first per-chat consent).
 >
-> Ready to proceed with Step 1 (`npm install -g memex-mvp`)?
+> Best path is the curl one-liner — does npm install (auto-fixes EACCES), daemon, auto-context hook, and history backfill in ~60 seconds. Want me to run:
+>
+> ```
+> curl -fsSL https://memex.parallelclaw.ai/install.sh | bash
+> ```
 >
 > **User:** yes
 >
-> **Agent:** [shows each command, runs npm install, gets `which memex` path, merges into `~/.cursor/mcp.json`, runs `memex-sync install`, runs `memex-sync scan`, prints restart hint]
+> **Agent:** [streams curl output, then edits `~/.cursor/mcp.json` to add `memex` MCP entry, prints restart hint, and offers Telegram capture setup]
 
 See [examples.md](examples.md) for more sample dialogues, including EACCES recovery and partial-install scenarios.
 

package/skills/install-memex/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: install-memex
-description: Make Claude, Cursor, Cline, Continue, and Zed remember every AI conversation forever — one local SQLite corpus shared across all of them. Installs memex (local-first MCP server) in ~2 minutes — npm install, MCP config wiring, auto-capture daemon, history backfill. No cloud, no account, verbatim storage. Also indexes Obsidian notes, Telegram chats, and any URL the user wants to save (web pages, Perplexity threads, AI chat shares — memex_store_document tool, v0.6+). Use when the user says "install memex", "set up memex", "add memory to my AI", "make my agent remember across sessions", or similar.
-version: 1.2.0
+description: Make Claude, Cursor, Cline, Continue, and Zed remember every AI conversation forever — one local SQLite corpus shared across all of them. Installs memex (local-first MCP server) in ~60 seconds via curl one-liner. Includes auto-capture daemon for Claude Code / Cowork / Cursor / Obsidian; v0.10 Telegram auto-detect (export from Desktop → memex stages it → AI proactively asks which to import, privacy-first per-chat consent); v0.8 SessionStart hook for the Brian Chesky moment ("Claude already knows what you were doing"); URL / Perplexity / AI chat share capture via memex_store_document. 18 MCP tools, no cloud, no account, verbatim storage. Use when the user says "install memex", "set up memex", "add memory to my AI", "make my agent remember across sessions", "сохрани мои чаты", or similar.
+version: 1.3.0
 metadata:
   openclaw:
     emoji: "📚"
@@ -225,16 +225,35 @@ If yes, run `memex_telegram_check` (MCP tool) or `memex telegram check` (CLI). T
   - **Logged in <24h ago?** → Tell them: "Telegram blocks export for the first 24h. Wait ~X hours, then come back."
   - **Ready to export?** → Show the click-path: open chat → ⋮ menu (top-right) → "Export chat history" → format HTML or JSON → Export.
 
-After the user exports, memex's daemon **auto-detects** the file in ~/Downloads/Telegram Desktop/ and stages it in pending review. Then:
+After the user exports, memex's daemon **auto-detects** the file in ~/Downloads/Telegram Desktop/ within ~7 seconds and stages it in `~/.memex/pending/`. Then:
 
   - Call `memex_telegram_pending` to list staged exports (chat name, msg count, date range).
-  - **Present as a numbered list**, ask which to import. Accept indices, titles, or natural language.
-  - Call `memex_telegram_import` with selected indices/titles. The chat is added to the allow-list — future re-exports auto-merge.
+  - **Present as a numbered list**, ask which to import. Accept indices, titles, or natural language ("import family and work, skip bank").
+  - Call `memex_telegram_import` with selected indices/titles. The chat is added to the allow-list — future re-exports auto-merge via UNIQUE(msg_id).
   - For sensitive chats user doesn't want (Bank, Therapist, etc.), call `memex_telegram_skip`.
 
+**Optional — clickable native macOS banner (v0.10.4+):** memex can fire a macOS notification the moment an export is staged. Default OFF for privacy. If the user wants this:
+
+```sh
+brew install terminal-notifier             # required for clickable banner
+memex telegram notifications on            # enable; default: titles hidden
+memex telegram notifications on --show-titles   # include chat names in banner
+```
+
+When enabled with `terminal-notifier`, clicking the banner opens (auto-detect priority): Claude Code CLI in a fresh Terminal tab → Claude Desktop → Terminal with `memex telegram pending`. The CLI launch path triggers the SessionStart hook → Brian Chesky moment. Override target: `memex telegram notifications target <auto|claude-cli|claude-desktop|terminal|none>`.
+
+**Other useful Telegram commands** (no MCP-tool wiring needed):
+
+```sh
+memex telegram check          # diagnostic: Desktop? login age (24h)? watcher?
+memex telegram open-pending   # one-shot: open pending list in best client
+memex telegram mode auto      # auto-import allow-listed chats on re-export
+memex telegram status         # decisions counts (allowed/skipped/blocked)
+```
+
 **Privacy is the core promise. Never auto-import. Always get explicit per-chat consent on the first round.**
 
-If the user declines Telegram setup ("not now" / "skip"): say "OK, I'll skip Telegram. You can run `memex telegram setup` anytime later." Don't push.
+If the user declines Telegram setup ("not now" / "skip"): say "OK, I'll skip Telegram. You can run `memex telegram check` anytime later to start." Don't push.
 
 ### 6. Tell the user what to do next
 
@@ -247,8 +266,12 @@ After restart, suggest they try any of:
 - "save https://en.wikipedia.org/wiki/As_We_May_Think to memex" → triggers `memex_store_document` and teaches the user that URL-saving exists (v0.6+)
 - **Open Claude Code in any project the user worked on recently** — the SessionStart auto-context (v0.8+) should kick in and Claude will mention prior work _before_ the user types anything. This is the "Brian Chesky moment" — the magical-first-impression of memex.
 
+- **(if Telegram was set up)** `memex telegram check` — confirms daemon's Telegram-Downloads watcher is active and shows the user's full capture pipeline state.
+
 These confirm everything works end-to-end.
 
+**Brian Chesky moment beyond Claude Code (v0.10.7+):** the SessionStart hook works only in Claude Code CLI. But starting v0.10.7, the same proactive behaviour is taught to agents in Cursor / Cline / Continue / Zed / Claude Desktop via SERVER_INSTRUCTIONS — these agents call `memex_overview` automatically on first interaction, read its `telegram_pending` field, and surface pending exports in their first reply. Slightly higher latency (one MCP roundtrip vs hook's instant inject), but same UX.
+
 **CLI fallback (v0.7+):** if the MCP integration doesn't pick up in the user's client for any reason, tell them they can verify memex from the terminal directly — same binary, no MCP needed:
 
 ```sh

package/skills/install-memex/examples.md

@@ -19,7 +19,7 @@ Sample interactions when the user invokes this skill. These show typical happy p
 > ✗ Continue / Zed not found
 > ```
 >
-> After install, memex will auto-index conversations from: **Claude Code, Cowork**. You can drop Telegram exports into `~/.memex/inbox/` later if needed.
+> After install, memex will auto-index conversations from: **Claude Code, Cowork**. v0.10+ also auto-detects Telegram Desktop exports — when you export a chat, I'll ask which to import.
 >
 > The fast path is a single hosted bash script that does **npm install (with EACCES auto-fix), daemon setup, Brian Chesky auto-context hook, history backfill, and `claude mcp add memex`** all in one go. Idempotent. Want me to run:
 >
@@ -64,7 +64,7 @@ Sample interactions when the user invokes this skill. These show typical happy p
 > ✗ Zed config not found
 > ```
 >
-> After install, memex will auto-index conversations from: **Claude Code, Cowork, Cursor**. If you also use Obsidian or want Telegram chats indexed, we can add those after the main install.
+> After install, memex will auto-index conversations from: **Claude Code, Cowork, Cursor**. v0.10+ Telegram capture also kicks in automatically — when you export a chat from Telegram Desktop, I'll ask which to import. If you also use Obsidian, we can wire that vault in after.
 >
 > Ready to proceed with Step 1?
 >