memex-mvp 0.10.9 → 0.10.11

package/ingest.js

@@ -293,6 +293,21 @@ async function cmdInstall() {
   console.log('');
   console.log(`config: ${CONFIG_PATH} (auto-created on first edit)`);
   console.log(`status: npx memex-sync status`);
+
+  // v0.10.10: surface the new web dashboard so manual installers actually
+  // discover it. (curl-bash flow has its own [Y/n] prompt in install.sh —
+  // it suppresses this output via `>/dev/null 2>&1`, so this callout is
+  // for the `memex-sync install` direct-call path only.)
+  console.log('');
+  console.log('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
+  console.log('🌐 NEW in v0.10.8: open your memory in a browser');
+  console.log('');
+  console.log('  memex web --open');
+  console.log('');
+  console.log('5 pages, read-only, localhost-only. Every captured');
+  console.log('conversation, verbatim — not summarized. Ctrl+C to stop.');
+  console.log('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
+
   process.exit(0);
 }
 

package/lib/cli/index.js

@@ -150,20 +150,41 @@ function maybePrintTelegramTip(opts = {}, currentSubcommand = '') {
 async function afterCommand(opts = {}, currentSubcommand = '') {
   if (opts.json) return;
   if (currentSubcommand === 'telegram') return;
+  if (currentSubcommand === 'web') return;     // web command holds the loop; tip would never print anyway
+  // `context` output IS the SessionStart hook payload — it gets injected
+  // verbatim into Claude Code's session header. Tips would corrupt that
+  // (and bust the --budget-tokens cap that the hook contract relies on).
+  if (currentSubcommand === 'context') return;
   if (process.env.MEMEX_TIP_SUPPRESS === '1') return;
   try {
-    const { listPending } = await import('../telegram-pending.js');
-    const list = listPending();
-    if (!list || list.length === 0) return;
     const notify = await import('../telegram-notify.js');
     const state = notify.loadNotifyState();
-    if (!notify.cliTipDue(state)) return;
-    const showTitles = state.notifications.show_titles !== false;
-    const tip = notify.formatTelegramTip(list, { showTitles });
-    if (tip) {
-      console.log(tip);
-      notify.markCliTipShown(state);
-      notify.saveNotifyState(state);
+
+    // Channel B priority: TG-pending tip first (it's actionable — there's
+    // a real export waiting). Dashboard tip is "nice to know", so only
+    // show it when the TG channel has nothing to surface.
+    const { listPending } = await import('../telegram-pending.js');
+    const list = listPending();
+    const hasPending = list && list.length > 0;
+
+    if (hasPending && notify.cliTipDue(state)) {
+      const showTitles = state.notifications.show_titles !== false;
+      const tip = notify.formatTelegramTip(list, { showTitles });
+      if (tip) {
+        console.log(tip);
+        notify.markCliTipShown(state);
+        notify.saveNotifyState(state);
+        return;
+      }
+    }
+
+    if (!hasPending && notify.dashboardTipDue(state)) {
+      const tip = notify.formatDashboardTip();
+      if (tip) {
+        console.log(c.dim(tip));
+        notify.markDashboardTipShown(state);
+        notify.saveNotifyState(state);
+      }
     }
   } catch (_) {
     /* never break a command because of a tip */
@@ -1737,6 +1758,18 @@ Examples:
 
   const { startServer } = await import('../web/index.js');
   await startServer(opts);
+
+  // First successful start ever → silence the discovery tip forever.
+  // User has clearly found the feature; no need to keep nagging.
+  try {
+    const notify = await import('../telegram-notify.js');
+    const state = notify.loadNotifyState();
+    if (!state.dashboard_ever_opened) {
+      notify.markDashboardEverOpened(state);
+      notify.saveNotifyState(state);
+    }
+  } catch (_) { /* never break server start on notify-state write */ }
+
   // The HTTP server now holds the event loop open. Park on an unsettled
   // promise so cmdWeb never returns to the dispatcher — that way server.js
   // doesn't reach process.exit(0) below or fall through to MCP-mode init.

package/lib/telegram-notify.js

@@ -47,6 +47,13 @@ const DEFAULT_STATE = () => ({
   version: 1,
   cli_tip_last_shown_at: null,
   notif_shown_for_ids: [],
+  // v0.10.10: dashboard discovery throttle. Three-strike pattern so the tip
+  // appears on a few different terminal sessions in the first days after
+  // install, then quiets down. Becomes permanently silent once the user
+  // actually opens the dashboard at least once.
+  dashboard_tip_shown_count: 0,
+  dashboard_tip_last_shown_at: null,
+  dashboard_ever_opened: false,
   notifications: {
     enabled: false,    // privacy-first: opt-in for macOS notification
     show_titles: false, // even when on, don't leak chat names by default
@@ -105,6 +112,49 @@ export function markCliTipShown(state, now = new Date()) {
   return state;
 }
 
+// ---------------------- Dashboard discovery tip (v0.10.10) ----------------------
+
+/**
+ * Whether the "try memex web" tip should fire on the next CLI command.
+ *
+ *   - Hard-stop once the user has actually run `memex web` (any duration)
+ *   - Cap at maxShows (default 3) total reveals
+ *   - Cooldown cooldownHours (default 12) between reveals so it doesn't
+ *     stack with the TG-pending tip on the same minute
+ */
+export function dashboardTipDue(state, opts = {}) {
+  const { maxShows = 3, cooldownHours = 12 } = opts;
+  if (state.dashboard_ever_opened) return false;
+  if ((state.dashboard_tip_shown_count || 0) >= maxShows) return false;
+  if (!state.dashboard_tip_last_shown_at) return true;
+  const last = Date.parse(state.dashboard_tip_last_shown_at);
+  if (isNaN(last)) return true;
+  return Date.now() - last >= cooldownHours * ONE_HOUR_MS;
+}
+
+export function markDashboardTipShown(state, now = new Date()) {
+  state.dashboard_tip_shown_count = (state.dashboard_tip_shown_count || 0) + 1;
+  state.dashboard_tip_last_shown_at = now.toISOString();
+  return state;
+}
+
+/**
+ * Permanently silence the dashboard tip — call this the first time the user
+ * actually runs `memex web`. They've discovered it; no need to keep nagging.
+ */
+export function markDashboardEverOpened(state) {
+  state.dashboard_ever_opened = true;
+  return state;
+}
+
+/**
+ * The tip text itself. Plain string (no ANSI) — the caller decides whether
+ * to dim it. Returns null if there is genuinely nothing to say (defensive).
+ */
+export function formatDashboardTip() {
+  return '💡 New: try `memex web --open` — browse your memory in a browser (read-only, localhost only).';
+}
+
 // ---------------------- Notification dedup ----------------------
 
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memex-mvp",
-  "version": "0.10.9",
+  "version": "0.10.11",
   "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",
@@ -26,7 +26,7 @@
     "sync": "node ingest.js",
     "ingest": "node ingest.js",
     "bot": "node bot/index.js",
-    "test": "node test/parser.test.js && node test/bot-inbox.test.js && node test/search-sort.test.js && node test/store-document.test.js && node test/cli.test.js && node test/hook.test.js && node test/telegram-html.test.js && node test/telegram-decisions.test.js && node test/telegram-pending.test.js && node test/telegram-notify.test.js && node test/notify-click-action.test.js",
+    "test": "node test/parser.test.js && node test/bot-inbox.test.js && node test/search-sort.test.js && node test/store-document.test.js && node test/cli.test.js && node test/hook.test.js && node test/telegram-html.test.js && node test/telegram-decisions.test.js && node test/telegram-pending.test.js && node test/telegram-notify.test.js && node test/notify-click-action.test.js && node test/inbox-watcher.test.js && node test/e2e-inbox.test.js",
     "prepublishOnly": "npm test"
   },
   "engines": {

package/server.js

@@ -810,18 +810,23 @@ function importFile(filePath) {
       Math.floor(Date.now() / 1000),
       imported
     );
+    log(`imported ${imported} messages from ${basename(filePath)} (${source})`);
+  } else {
+    log(`no NEW messages from ${basename(filePath)} (all dupes)`);
+  }
 
-    // Move processed file to archive
+  // Move processed file to archive regardless of imported count. If we only
+  // archive when imported>0, a fully-deduplicated snapshot stays in inbox.
+  // Daemon then overwrites that file periodically — and on filesystems where
+  // rename-over-existing only fires chokidar 'change' (not 'add'), the
+  // 'change' listener above re-imports, fine; but it also means a wasted
+  // file accumulates in inbox if for any reason the listener didn't catch.
+  // Archiving always keeps inbox a clean "what's new" queue.
+  if (source !== 'unknown') {
     const targetDir = join(ARCHIVE, source);
     mkdirSync(targetDir, { recursive: true });
     const target = join(targetDir, basename(filePath));
-    try {
-      renameSync(filePath, target);
-    } catch (_) {}
-
-    log(`imported ${imported} messages from ${basename(filePath)} (${source})`);
-  } else {
-    log(`no messages imported from ${basename(filePath)}`);
+    try { renameSync(filePath, target); } catch (_) {}
   }
   return imported;
 }
@@ -852,6 +857,19 @@ chokidar
     log('inbox detected (file):', basename(filePath));
     importFile(filePath);
   })
+  // 'change' is critical: the ingest daemon overwrites the inbox snapshot
+  // file every few seconds as the underlying Claude Code / Cowork JSONL
+  // grows (the snapshot is a full re-serialisation, not a delta append).
+  // Without a 'change' listener, chokidar only fires 'add' once when the
+  // file first appears — every subsequent overwrite is silent, the inbox
+  // file accumulates new content on disk but server.js never re-imports
+  // it. UNIQUE(source, conv, msg_id) + INSERT OR IGNORE keep repeated
+  // imports idempotent, so re-processing the whole file on every change
+  // is correct (and cheap: SQLite handles ~10k rows in tens of ms).
+  .on('change', (filePath) => {
+    log('inbox changed (file):', basename(filePath));
+    importFile(filePath);
+  })
   .on('addDir', (dirPath) => {
     // Skip the inbox itself
     if (dirPath === INBOX) return;

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 ~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.4.0
+version: 1.4.1
 metadata:
   openclaw:
     emoji: "📚"
@@ -290,15 +290,19 @@ If the user declines Telegram setup ("not now" / "skip"): say "OK, I'll skip Tel
 
 Tell the user to fully quit and reopen the MCP client (Cmd+Q on macOS) so it picks up the new memex tools.
 
-After restart, suggest they try any of:
+**🌟 FIRST, STRONGLY RECOMMEND THIS (v0.10.8+):** offer to run `memex web --open` for them right now. It's the single most magical post-install moment — a local browser tab opens at `http://127.0.0.1:8765` with 5 pages showing every conversation memex has captured, dialogue rendered as chat-bubbles, full-text searchable. Verbatim — not AI-summarized. Read-only, localhost-only, Ctrl+C to stop. Phrase it naturally, e.g.:
+
+> "I can open a local web dashboard that lets you actually *see* what memex captured — every message, in chat-bubble form, searchable. It's just a browser tab on `localhost:8765`. Run it now? It's a way better demo than asking me search queries blind."
+
+Then run `memex web --open` (in a backgrounded shell if your shell wrapper supports it — otherwise tell the user to run it themselves in another terminal). Wait for them to react before continuing.
+
+**After that, suggest other ways to confirm end-to-end:**
 - "show me what memex has in memory" → triggers `memex_overview`
 - "what projects has memex captured" → triggers `memex_list_projects`
 - "search memex for [recent topic]" → triggers `memex_search`
 - "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.
-- **(v0.10.8+)** `memex web --open` — opens the local read-only web dashboard at `http://127.0.0.1:8765`. 5 pages: corpus stats, FTS5-searchable conversations list, verbatim chat-bubble transcripts, pending Telegram review with checkboxes, settings/daemon status. Useful for the user to *see* their memory with their own eyes — and a strong demo moment ("look at the actual messages verbatim, not an AI summary"). Localhost-only by default; Ctrl+C to stop.
 
 These confirm everything works end-to-end.