commandmate 0.45.0 → 0.45.1

package/dist/server/src/lib/polling/response-checker.js

@@ -491,6 +491,15 @@ function extractCompletedTurn(ctx, output, lastCapturedLine) {
     // Extract response
     const result = extractResponse(output, lastCapturedLine, cliToolId, tmux_capture_cache_1.CACHE_MAX_CAPTURE_LINES);
     if (!result || !result.isComplete) {
+        // Issue #3538: an unfinished frame was read and carries no live prompt (the
+        // early prompt check in `extractResponse` would have returned it complete),
+        // so a run of duplicate prompt ticks is over; the hash is kept — see the
+        // helper. Only when the frame WAS read: a null result is extraction being
+        // skipped on the line count ("no new output"), which says nothing about
+        // whether the prompt is still on screen, and neither do the cursor returns
+        // further down.
+        if (result)
+            (0, prompt_dedup_1.resetDuplicatePromptSkipStreak)(pollerKey);
         // DR-004 windowing: Only check tail lines
         const { thinkingPattern } = (0, cli_patterns_1.getCliToolPatterns)(cliToolId);
         const cleanOutput = (0, cli_patterns_1.stripAnsi)(output);
@@ -565,7 +574,19 @@ function savePromptMessage(ctx, promptDetection, result, isFullScreenTui) {
         // classified (#1676) look identical from the CLI — both say "nothing was
         // recorded". Count the skip so the payload can tell them apart.
         (0, prompt_dedup_state_1.recordPromptDedupSkip)(worktreeId, cliToolId, instanceId);
-        logger.info('duplicate-prompt-skipped', { worktreeId, cliToolId });
+        // Issue #3538: the tally above is counted on every tick; the log line is
+        // not. A full-screen TUI sits on its prompt for as long as it stays
+        // unanswered, a duplicate every 2 s. The first tick of a run logs exactly
+        // as before; after that one line per `DUPLICATE_PROMPT_SKIP_LOG_TICK_INTERVAL`
+        // ticks, with the run length and how many ticks went unlogged (#3519).
+        const skipLog = (0, prompt_dedup_1.claimDuplicatePromptSkipLog)(pollerKey);
+        if (skipLog.log) {
+            logger.info('duplicate-prompt-skipped', {
+                worktreeId,
+                cliToolId,
+                ...(skipLog.consecutive > 1 ? { consecutive: skipLog.consecutive, suppressed: skipLog.suppressed } : {}),
+            });
+        }
         return false;
     }
     // Issue #571: Clean TUI decorations from Copilot prompt content before saving
@@ -723,7 +744,21 @@ async function recheckDuplicateResponse(ctx, result, claudeMetadata) {
     // logged nothing at all, so a reply that never reached History left no
     // trace anywhere. Same action name shape as its sibling so both skips
     // are found by one grep.
-    logger.info('duplicate-response-skipped', { worktreeId, cliToolId, instanceId: resolvedInstanceId });
+    //
+    // Issue #3519: but not on every tick. A finished screen that stays up is a
+    // duplicate on each of the cycle's 900 ticks, and logging all of them was
+    // 51,933 lines a day. The first tick of a run logs exactly as before; after
+    // that one line per `DUPLICATE_RESPONSE_SKIP_LOG_TICK_INTERVAL` ticks, with
+    // the run length and how many ticks went unlogged since the last line.
+    const skipLog = (0, response_dedup_1.claimDuplicateResponseSkipLog)(pollerKey);
+    if (skipLog.log) {
+        logger.info('duplicate-response-skipped', {
+            worktreeId,
+            cliToolId,
+            instanceId: resolvedInstanceId,
+            ...(skipLog.consecutive > 1 ? { consecutive: skipLog.consecutive, suppressed: skipLog.suppressed } : {}),
+        });
+    }
     (0, db_1.updateSessionState)(db, worktreeId, cliToolId, result.lineCount, resolvedInstanceId);
     // Issue #2399: the skip above is about the SCREEN, and until this Issue
     // it also ended the tick for the TRANSCRIPT READER 100 lines below —
@@ -1156,6 +1191,9 @@ async function checkForResponse(worktreeId, cliToolId, instanceId) {
         if (promptIsLive) {
             return savePromptMessage(ctx, promptDetection, result, isFullScreenTui);
         }
+        // Issue #3538: a finished frame without a live prompt ends the run of
+        // duplicate prompt ticks, as an unfinished one does in `extractCompletedTurn`.
+        (0, prompt_dedup_1.resetDuplicatePromptSkipStreak)(pollerKey);
         // Validate response content is not empty
         if (!result.response || result.response.trim() === '') {
             (0, db_1.updateSessionState)(db, worktreeId, cliToolId, result.lineCount, resolvedInstanceId);

package/dist/server/src/lib/polling/response-dedup.js

@@ -39,10 +39,22 @@
  * hash, and the worktree rename all have to treat the two the same, and the
  * only way to guarantee that without touching `response-poller-core` (which
  * owns those three calls) is for one function to clear both.
+ *
+ * ## The third cache: how often the skip says so (#3519)
+ *
+ * The skip logs `duplicate-response-skipped` so a reply missing from History
+ * leaves a grep-able trace (#1695). Logged on every tick, a screen that stays
+ * up writes that line every 2 s for the whole cycle — 51,933 lines in 24 h,
+ * 80% of the server log. The run of duplicate ticks is counted here so the line
+ * is written on the first tick of a run and then once per
+ * {@link DUPLICATE_RESPONSE_SKIP_LOG_TICK_INTERVAL} ticks. The count is about
+ * one particular cached hash, so it lives and dies with it for the same reason
+ * the recheck does.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.STRUCTURED_HISTORY_RECHECK_TICK_INTERVAL = void 0;
+exports.DUPLICATE_RESPONSE_SKIP_LOG_TICK_INTERVAL = exports.STRUCTURED_HISTORY_RECHECK_TICK_INTERVAL = void 0;
 exports.isDuplicateResponse = isDuplicateResponse;
+exports.claimDuplicateResponseSkipLog = claimDuplicateResponseSkipLog;
 exports.markStructuredHistoryRecheckPending = markStructuredHistoryRecheckPending;
 exports.settleStructuredHistoryRecheck = settleStructuredHistoryRecheck;
 exports.claimStructuredHistoryRecheck = claimStructuredHistoryRecheck;
@@ -79,6 +91,25 @@ const structuredHistoryRecheckCache = (0, global_state_1.getOrInitGlobal)('__str
  * or the cycle ends, the entry is gone.
  */
 exports.STRUCTURED_HISTORY_RECHECK_TICK_INTERVAL = 3;
+/**
+ * In-memory cache: pollerKey -> how many duplicate ticks in a row the current
+ * cached hash has been skipped (Issue #3519). Absence means none yet.
+ *
+ * On `globalThis` for the same reason `responseHashCache` is, and cleared and
+ * moved at exactly the same moments — see the module comment. A new
+ * (non-duplicate) response restarts it in {@link isDuplicateResponse}.
+ */
+const duplicateResponseSkipStreak = (0, global_state_1.getOrInitGlobal)('__duplicateResponseSkipStreak', () => new Map());
+/**
+ * How many duplicate ticks separate two `duplicate-response-skipped` lines
+ * (Issue #3519).
+ *
+ * At the poller's 2 s tick this is one line a minute while a finished screen
+ * stays up, so a 900-tick cycle writes 30 lines instead of 899. The first tick
+ * of a run always logs, so the #1695 trace — "this reply was skipped, at this
+ * time" — is still there for every run; what is dropped is the repetition.
+ */
+exports.DUPLICATE_RESPONSE_SKIP_LOG_TICK_INTERVAL = 30;
 /**
  * Check whether the given response content was already saved during the current
  * polling cycle for the same pollerKey. If it is new, updates the cache.
@@ -93,8 +124,30 @@ function isDuplicateResponse(pollerKey, content) {
         return true;
     }
     responseHashCache.set(pollerKey, hash);
+    // Issue #3519: a new response starts a new run of duplicate ticks.
+    duplicateResponseSkipStreak.delete(pollerKey);
     return false;
 }
+/**
+ * Count one duplicate tick for this pollerKey and say whether it should be
+ * logged (Issue #3519).
+ *
+ * A claim, like {@link claimStructuredHistoryRecheck}: it advances the count, so
+ * call it exactly once per duplicate tick. Logs on the first tick of a run and
+ * then on every {@link DUPLICATE_RESPONSE_SKIP_LOG_TICK_INTERVAL}th tick after
+ * it (ticks 1, 1+N, 1+2N, …).
+ *
+ * @param pollerKey - Poller key ("worktreeId:instanceId")
+ * @returns Whether to log, the run length so far, and the ticks left unlogged
+ *   since the previous line
+ */
+function claimDuplicateResponseSkipLog(pollerKey) {
+    const consecutive = (duplicateResponseSkipStreak.get(pollerKey) ?? 0) + 1;
+    duplicateResponseSkipStreak.set(pollerKey, consecutive);
+    const log = (consecutive - 1) % exports.DUPLICATE_RESPONSE_SKIP_LOG_TICK_INTERVAL === 0;
+    const suppressed = consecutive === 1 ? 0 : exports.DUPLICATE_RESPONSE_SKIP_LOG_TICK_INTERVAL - 1;
+    return { log, consecutive, suppressed };
+}
 /**
  * Note that the transcript reader has unfinished business for this pollerKey
  * (Issue #2399).
@@ -177,6 +230,8 @@ function claimStructuredHistoryRecheck(pollerKey) {
 function clearResponseHashCache(pollerKey) {
     responseHashCache.delete(pollerKey);
     structuredHistoryRecheckCache.delete(pollerKey);
+    // Issue #3519: the skip count is about the same hash.
+    duplicateResponseSkipStreak.delete(pollerKey);
 }
 /**
  * Move the cached hash from one pollerKey to another.
@@ -206,4 +261,10 @@ function renameResponseHashCacheKey(oldKey, newKey) {
     structuredHistoryRecheckCache.delete(oldKey);
     if (ticksToWait !== undefined)
         structuredHistoryRecheckCache.set(newKey, ticksToWait);
+    // Issue #3519: the skip count moves with the hash too, so a rename mid-run
+    // does not restart the thinning and log as if a new run had begun.
+    const streak = duplicateResponseSkipStreak.get(oldKey);
+    duplicateResponseSkipStreak.delete(oldKey);
+    if (streak !== undefined)
+        duplicateResponseSkipStreak.set(newKey, streak);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "commandmate",
-  "version": "0.45.0",
+  "version": "0.45.1",
   "description": "No long blocks of time? Run an AI team from your phone. Git worktree sessions, task contracts and verification gates for Claude Code, Codex, Gemini CLI, Copilot, OpenCode, Antigravity and Command Code.",
   "keywords": [
     "ai-agents",

package/release-notes/0.45.1.json

@@ -0,0 +1,38 @@
+{
+  "version": "0.45.1",
+  "date": "2026-10-10",
+  "highlight": {
+    "ja": "チャットと履歴で mermaid の図が描かれるようになり、履歴検索の強調が正しい位置に当たるようになりました。",
+    "en": "Mermaid diagrams now render in chat and History, and History search highlights now land on the right text."
+  },
+  "added": [
+    {
+      "ja": "チャットの回答と履歴で、mermaid のコードが図として表示されるようになりました（ダークテーマにも対応）。",
+      "en": "Mermaid code in chat answers and History is now drawn as a diagram, including in the dark theme."
+    },
+    {
+      "ja": "ファイルを単独で開いたページでも、mermaid のコードが図として表示されるようになりました。",
+      "en": "Mermaid code is now drawn as a diagram when a file is opened on its own page."
+    }
+  ],
+  "improved": [
+    {
+      "ja": "画面が止まっている間に同じ内容のログが繰り返し出ていたのを減らし、サーバーのログ量を大きく減らしました。",
+      "en": "The server log no longer repeats the same line while a screen stays unchanged, which greatly reduces its size."
+    }
+  ],
+  "fixed": [
+    {
+      "ja": "履歴検索の強調が、太字やリンクなどの記法の文字数だけずれていた問題を直しました。",
+      "en": "Fixed History search highlights being shifted by the length of formatting such as bold text and links."
+    },
+    {
+      "ja": "履歴検索で、mermaid の図の中のヒットが強調されないことがある問題を直しました。",
+      "en": "Fixed History search sometimes not highlighting matches inside mermaid diagrams."
+    },
+    {
+      "ja": "スキルのフォルダに説明ファイルが無いだけで、サーバーのログにエラーが出ていた問題を直しました。",
+      "en": "Fixed the server log reporting an error for skill folders that simply have no description file."
+    }
+  ]
+}