chat-recall 0.5.4 → 0.5.6

package/hooks/chat_recall_escalate_hook.sh

@@ -33,6 +33,32 @@ fi
 CHAT_RECALL_BIN="${CHAT_RECALL_BIN:-$(command -v chat-recall || true)}"
 if [[ -z "$CHAT_RECALL_BIN" ]] || [[ ! -x "$CHAT_RECALL_BIN" ]]; then exit 0; fi
 
+# Run a command under a time limit, on any platform.
+#
+# `timeout` is GNU coreutils and macOS does not ship it. Both hooks that used it
+# swallowed the failure with `|| true`, so on every Mac the command never ran at
+# all — silently, while `chat-recall doctor` reported the hook installed and
+# healthy. Homebrew's coreutils installs it as `gtimeout`, so prefer whichever
+# exists and fall back to a plain shell watchdog when neither does.
+run_limited() {
+  local secs="$1"; shift
+  if command -v timeout >/dev/null 2>&1; then
+    timeout "$secs" "$@"
+  elif command -v gtimeout >/dev/null 2>&1; then
+    gtimeout "$secs" "$@"
+  else
+    # Watchdog: run in the background, kill it if it outlives the budget.
+    "$@" &
+    local cmd_pid=$!
+    ( sleep "$secs"; kill -TERM "$cmd_pid" 2>/dev/null || true ) &
+    local watch_pid=$!
+    wait "$cmd_pid" 2>/dev/null
+    local rc=$?
+    kill -TERM "$watch_pid" 2>/dev/null || true
+    return $rc
+  fi
+}
+
 TIMEOUT="${CHAT_RECALL_ESCALATE_TIMEOUT:-60}"
 DELAY="${CHAT_RECALL_ESCALATE_DELAY:-20}"
 
@@ -42,9 +68,9 @@ DELAY="${CHAT_RECALL_ESCALATE_DELAY:-20}"
   sleep "$DELAY"
   cd "$CWD" 2>/dev/null || true
   if [[ -n "$SESSION_ID" ]]; then
-    timeout "$TIMEOUT" "$CHAT_RECALL_BIN" escalate "$SESSION_ID" >/dev/null 2>&1 || true
+    run_limited "$TIMEOUT" "$CHAT_RECALL_BIN" escalate "$SESSION_ID" >/dev/null 2>&1 || true
   else
-    timeout "$TIMEOUT" "$CHAT_RECALL_BIN" escalate --latest >/dev/null 2>&1 || true
+    run_limited "$TIMEOUT" "$CHAT_RECALL_BIN" escalate --latest >/dev/null 2>&1 || true
   fi
 ) </dev/null >/dev/null 2>&1 &
 

package/hooks/chat_recall_save_hook.sh

@@ -109,7 +109,7 @@ extract_facts() {
   "tool_uses": $tools,
   "first_topic": "$(echo "$first_topic" | jq -Rs '.' 2>/dev/null || echo "\"$first_topic\"")",
   "decisions": "$(echo "$decisions" | jq -Rs '.' 2>/dev/null || echo "\"\"")",
-  "saved_at": "$(date -Iseconds)"
+  "saved_at": "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
 }
 EOF
 }
@@ -176,7 +176,12 @@ do_save() {
     fi
     
     # Track this save
-    echo "{\"session_id\": \"$SESSION_ID\", \"saved_at\": \"$(date -Iseconds)\", \"precompact\": $precompact}" > "${STATE_FILE}"
+    # `date -Iseconds` is GNU-only: BSD date (macOS) rejects -I and prints an
+    # empty string, so this field was blank on every Mac. -u +format works on
+    # both. saved_at_epoch is written alongside it because reading the ISO value
+    # BACK needed `date -d`, which BSD also lacks — storing the number means
+    # nothing has to parse a date at all.
+    echo "{\"session_id\": \"$SESSION_ID\", \"saved_at\": \"$(date -u +%Y-%m-%dT%H:%M:%SZ)\", \"saved_at_epoch\": $(date +%s), \"precompact\": $precompact}" > "${STATE_FILE}"
     
     if [[ "$precompact" == "true" ]]; then
         log "[PRECOMPACT] Emergency save for $SESSION_ID"
@@ -193,17 +198,18 @@ should_save() {
         return 0
     fi
     
-    # Check last save time
-    local last_save
-    last_save=$(jq -r '.saved_at // empty' "${STATE_FILE}" 2>/dev/null || echo "")
-    
-    if [[ -z "$last_save" ]]; then
+    # Read the epoch we stored. The old code kept only an ISO string and parsed
+    # it with `date -d`, which does not exist on BSD date — so on macOS this
+    # always resolved to 0, the throttle never engaged, and the hook re-scanned
+    # the entire transcript on EVERY Stop event.
+    local last_save_epoch
+    last_save_epoch=$(jq -r '.saved_at_epoch // empty' "${STATE_FILE}" 2>/dev/null || echo "")
+
+    if [[ -z "$last_save_epoch" ]]; then
+        # A state file written before saved_at_epoch existed. Treat it as due
+        # rather than trying to parse its timestamp portably.
         return 0
     fi
-    
-    # Don't save more than once per 30 seconds
-    local last_save_epoch
-    last_save_epoch=$(date -d "$last_save" +%s 2>/dev/null || echo 0)
     local now_epoch
     now_epoch=$(date +%s)
     

package/hooks/chat_recall_wakeup_hook.sh

@@ -27,7 +27,33 @@ CHAT_RECALL_BIN="${CHAT_RECALL_BIN:-$(command -v chat-recall || true)}"
 if [[ -z "$CHAT_RECALL_BIN" ]] || [[ ! -x "$CHAT_RECALL_BIN" ]]; then exit 0; fi
 
 TIMEOUT="${CHAT_RECALL_WAKEUP_TIMEOUT:-10}"
-OUT="$(timeout "$TIMEOUT" "$CHAT_RECALL_BIN" memory wake-up -p "$PROJECT" 2>/dev/null || true)"
+# Run a command under a time limit, on any platform.
+#
+# `timeout` is GNU coreutils and macOS does not ship it. Both hooks that used it
+# swallowed the failure with `|| true`, so on every Mac the command never ran at
+# all — silently, while `chat-recall doctor` reported the hook installed and
+# healthy. Homebrew's coreutils installs it as `gtimeout`, so prefer whichever
+# exists and fall back to a plain shell watchdog when neither does.
+run_limited() {
+  local secs="$1"; shift
+  if command -v timeout >/dev/null 2>&1; then
+    timeout "$secs" "$@"
+  elif command -v gtimeout >/dev/null 2>&1; then
+    gtimeout "$secs" "$@"
+  else
+    # Watchdog: run in the background, kill it if it outlives the budget.
+    "$@" &
+    local cmd_pid=$!
+    ( sleep "$secs"; kill -TERM "$cmd_pid" 2>/dev/null || true ) &
+    local watch_pid=$!
+    wait "$cmd_pid" 2>/dev/null
+    local rc=$?
+    kill -TERM "$watch_pid" 2>/dev/null || true
+    return $rc
+  fi
+}
+
+OUT="$(run_limited "$TIMEOUT" "$CHAT_RECALL_BIN" memory wake-up -p "$PROJECT" 2>/dev/null || true)"
 [[ -z "$OUT" ]] && exit 0
 
 {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chat-recall",
-  "version": "0.5.4",
+  "version": "0.5.6",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/munhq/chat-recall.git"
@@ -11,6 +11,9 @@
   },
   "description": "Local-first memory for AI coding tools \u2014 indexes Claude Code / Gemini CLI / OpenCode / Codex sessions, exposes them over MCP, optionally syncs redacted history to a chat-recall server",
   "type": "module",
+  "engines": {
+    "node": ">=22.5.0"
+  },
   "license": "Elastic-2.0",
   "bin": {
     "chat-recall": "./dist/cli.js",
@@ -25,9 +28,10 @@
     "LICENSE"
   ],
   "scripts": {
-    "build": "tsc -b && node scripts/bundle.mjs && node scripts/postbuild.mjs",
+    "build": "tsc -b && tsc -p tsconfig.daemon.json && node scripts/bundle.mjs && node scripts/postbuild.mjs",
     "build:types": "tsc -b",
-    "auto-indexer": "tsx auto-indexer/indexer.ts"
+    "auto-indexer": "tsx auto-indexer/indexer.ts",
+    "typecheck:daemon": "tsc -p tsconfig.daemon.json"
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.0.0",

package/skills/chat-recall/SKILL.md

@@ -31,6 +31,7 @@ read except these, which change stored memory or state — treat each as an edit
 and apply the test in `chat-recall-memory` before calling one:
 `recall_kg_add`, `recall_kg_invalidate`, `recall_decision_record`,
 `recall_diary_write`, `recall_set`, `recall_task_create`, `recall_task_update`,
+`recall_task_comment`,
 `recall_security_dismiss`, `recall_rename_session`, `recall_regenerate_summary`,
 `recall_reclassify`, `recall_index`, `recall_code_index`.
 
@@ -65,9 +66,9 @@ tool is registered and never named here, so adding a tool means placing it.
 **Findings, ranked** — `recall_claude_suggestions` (every finding that becomes an agent-instruction change — the CLAUDE.md rules and skill installs — merged across account scope and every indexed project) and `recall_improvements` (everything else, most urgent first; `create_tasks: true` opens one team task per item). They split the same engines, so an item never appears in both. Neither needs the codeindex binary: without it you still get the account-level half.
 **What changed** — `recall_edits_timeline` (cross-tool edits), `recall_diff` (per-session diffs), `recall_commits` (did it actually land), `recall_markers` (where a session went sideways).
 **Durable memory / KG** — `recall_kg_query` / `recall_kg_add` / `recall_kg_invalidate` / `recall_kg_timeline` / `recall_kg_stats`, `recall_decision_record`, `recall_diary_write` / `recall_diary_read`, `recall_set` / `recall_get`.
-**Team** — `recall_tasks` (the shared task board), `recall_task_create`, `recall_task_update` (status, assignee, comment; task ids look like `t_…`), `recall_team_activity` (per-teammate × per-project rollup), `recall_shares` (which projects are shared — private by default, nothing is visible to teammates until shared).
+**Team** — `recall_tasks` (the shared task board), `recall_task_create`, `recall_task_update` (status, assignee, linked session; task ids look like `t_…`; when you start work on a task, set it `in_progress` and pass your session id as `linked_session_id` so the board can verify the work shipped), `recall_task_comment` (leave a progress note on a card), `recall_team_activity` (per-teammate × per-project rollup), `recall_shares` (which projects are shared — private by default, nothing is visible to teammates until shared).
 **Security** — `recall_security_summary` (leaked secrets that still need action — start here for "did I paste a key somewhere"), `recall_security_session` (findings for one session), `recall_security_dismiss` (mark rotated / false positive — do this only when the user confirms which), `recall_security_rules` (tenant detection rules; also tests a regex).
-**Health / maintenance** — `recall_status` (is the index alive, what is synced), `recall_index` (sync now), `recall_heal_audit` (sessions whose rendered text is thinner than the raw archive, i.e. truncated upstream), `recall_regenerate_summary` (stored summary is stale or wrong), `recall_reclassify` (re-run the classifier over old chunks), `recall_rename_session`.
+**Health / maintenance** — `recall_status` (is the index alive, what is synced), `recall_index` (sync now), `recall_help` (names the tools the lean profile leaves unlisted — they all still work by name), `recall_heal_audit` (sessions whose rendered text is thinner than the raw archive, i.e. truncated upstream), `recall_regenerate_summary` (stored summary is stale or wrong), `recall_reclassify` (re-run the classifier over old chunks), `recall_rename_session`.
 
 ## If you're unsure where to start