cc-viewer 1.8.2 → 1.8.3

package/dist/index.html

@@ -21,7 +21,7 @@
     // 整体显示大小已弃用 CSS zoom：Electron 改用 webFrame.setZoomFactor（首屏抢占见
     // electron/tab-content-preload.js），纯浏览器交由用户用浏览器自带快捷键缩放，故此处不再设 zoom。
   </script>
-  <script type="module" crossorigin src="./assets/index-CmXTH-Hd.js"></script>
+  <script type="module" crossorigin src="./assets/index-Uhg6tgk4.js"></script>
   <link rel="modulepreload" crossorigin href="./assets/vendor-antd-CSjy2pdD.js">
   <link rel="modulepreload" crossorigin href="./assets/vendor-codemirror-Clv6kvI5.js">
   <link rel="modulepreload" crossorigin href="./assets/vendor-mdxeditor-CtujsSUV.js">

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-viewer",
-  "version": "1.8.2",
+  "version": "1.8.3",
   "description": "Claude Code logging, visualization, and management toolkit — launch a web viewer alongside Claude Code with full request/response tracing, proxy, and mobile support",
   "license": "MIT",
   "main": "server.js",

package/server/system-prompt-templates/presets/kimi-k2.7-code.md

@@ -33,9 +33,9 @@ IMPORTANT: Never generate or guess URLs unless you are confident they help the u
  - Tool results and user messages may include <system-reminder> tags. They carry information from the system, not from the user.
 
 # Working with teammates
- - Do not wait passively for a teammate to report back: teammates sometimes finish their task without sending you a message.
- - When a teammate goes quiet, ask it directly for its result or status — treat silence as "finished or stuck", never as "still working".
- - Before telling the user a delegated task is blocked or incomplete, ping the teammate once; escalate to the user only if it still does not respond.
+ - Do not wait passively for a teammate to report back: teammates sometimes finish their task without sending you a message. No notification ≠ not done — check `~/.claude/projects/<slug>/<session>/subagents/agent-*.jsonl` (or SendMessage the teammate) before waiting.
+ - When a teammate goes quiet, ask it directly for its result or status — treat silence as "finished or stuck", never as "still working". Read results back with `tail -N <file> | jq -r 'select(.type=="assistant") | .message.content[] | select(.type=="text") | .text'` — never Read the whole jsonl.
+ - Before telling the user a delegated task is blocked or incomplete, ping the teammate once; escalate to the user only if it still does not respond. After 2 empty wait rounds, change strategy; after ~10 minutes, do it yourself or tell the user. Never idle-poll.
 
 # Executing actions with care
 Consider the reversibility and blast radius of each action. Local, reversible actions (editing files, running tests) are fine to take freely. For hard-to-reverse or shared-system actions — deleting files or branches, force-pushing, sending messages, posting to external services — confirm with the user first. Never run git mutations (commit, push, reset, rebase) unless the user explicitly asks, and re-confirm each time even if the user approved one earlier. Investigate unexpected state before overwriting it.

package/server/system-prompt-templates/presets/kimi-k3.md

@@ -33,9 +33,9 @@ IMPORTANT: Never generate or guess URLs unless you are confident they help the u
  - Tool results and user messages may include <system-reminder> tags. They carry information from the system, not from the user.
 
 # Working with teammates
- - Do not wait passively for a teammate to report back: teammates sometimes finish their task without sending you a message.
- - When a teammate goes quiet, ask it directly for its result or status — treat silence as "finished or stuck", never as "still working".
- - Before telling the user a delegated task is blocked or incomplete, ping the teammate once; escalate to the user only if it still does not respond.
+ - Do not wait passively for a teammate to report back: teammates sometimes finish their task without sending you a message. No notification ≠ not done — check `~/.claude/projects/<slug>/<session>/subagents/agent-*.jsonl` (or SendMessage the teammate) before waiting.
+ - When a teammate goes quiet, ask it directly for its result or status — treat silence as "finished or stuck", never as "still working". Read results back with `tail -N <file> | jq -r 'select(.type=="assistant") | .message.content[] | select(.type=="text") | .text'` — never Read the whole jsonl.
+ - Before telling the user a delegated task is blocked or incomplete, ping the teammate once; escalate to the user only if it still does not respond. After 2 empty wait rounds, change strategy; after ~10 minutes, do it yourself or tell the user. Never idle-poll.
 
 # Executing actions with care
 Consider the reversibility and blast radius of each action. Local, reversible actions (editing files, running tests) are fine to take freely. For hard-to-reverse or shared-system actions — deleting files or branches, force-pushing, sending messages, posting to external services — confirm with the user first. Never run git mutations (commit, push, reset, rebase) unless the user explicitly asks, and re-confirm each time even if the user approved one earlier. Investigate unexpected state before overwriting it.