agenthud 0.9.1 → 0.9.3

package/dist/templates/summary-prompt.md

@@ -1,12 +1,37 @@
-The following is an activity log of work done with Claude Code. Summarize it concisely in English using the format below.
+The following is an activity log from a single day of Claude Code sessions.
+Each entry: `[HH:MM] <icon> <label>: <detail>`. Icons indicate activity type (◆ = git commit).
 
-## Completed Work
-- (What was accomplished — focus on Response entries)
+Write a concise but high-signal engineering summary in English.
+Aim for roughly 300-500 words total — favor synthesis over completeness.
 
-## Notable Changes
-- (Which files were modified and how — from Edit/Write entries)
+Focus on:
+- meaningful accomplishments
+- debugging discoveries
+- architectural decisions
+- implementation progress
+- important tradeoffs or realizations
+- unfinished work and next steps
 
-## Commits
-- (Summary of the ◆ commit lines)
+Do NOT mechanically summarize every edit, response, or commit.
+Do NOT list every modified file.
+Omit any section that has no substantive content — do not emit placeholders like "None" or "N/A".
+Prefer high-level synthesis grouped by theme or workstream.
+
+Use the following format:
+
+## Context
+What was the primary goal or investigation today?
+
+## Key Accomplishments
+Meaningful progress, completed implementations, resolved issues.
+
+## Technical Insights
+Important debugging findings, architectural decisions, tradeoffs, or discoveries.
+
+## Major Code Changes
+Significant codebase or subsystem changes, grouped by theme. Reference relevant commits inline where useful (e.g. `abc1234`). Do not enumerate every commit.
+
+## Open Questions / Next Steps
+Only include items explicitly stated in the log or strongly implied by an unfinished workflow. Do not invent generic follow-ups ("consider refactoring X").
 
 Activity log:

package/dist/templates/summary-range-prompt.md

@@ -0,0 +1,35 @@
+The following are daily engineering summaries from a date range, separated by `---` lines.
+Each daily summary uses the structure: Context / Key Accomplishments / Technical Insights / Major Code Changes / Open Questions.
+
+Write a range-level synthesis in English.
+Aim for roughly 400-700 words total — the value of a range summary is cross-day pattern extraction, not re-summarization.
+
+Do NOT concatenate or restate the daily summaries.
+Do NOT produce a per-day timeline ("On Monday X, on Tuesday Y...").
+Do NOT report a day's cache/auth/load status (e.g. "cached", "not logged in", "no activity") as if it were the day's content. Such phrases reflect tooling state, not engineering work — exclude them entirely. If a day has no substantive content, just don't mention it.
+Omit any section that has no substantive content.
+
+The point of a range summary is to surface what only becomes visible by looking across days:
+- threads of work that spanned multiple days
+- recurring debugging patterns or repeated tradeoffs
+- outcomes that matter at the range level, not at any single day
+- work that started in one day and continued, completed, or was abandoned later
+
+Use the following format:
+
+## Range Overview
+What date range this covers and the dominant theme of the period. 1-3 sentences.
+
+## Major Outcomes
+The 3-5 most significant results of the range. Consolidate across days; do not attribute to specific dates unless meaningful.
+
+## Workstreams
+Multi-day initiatives or investigations. For each: what it was, how it evolved across the range, and where it ended (shipped, paused, abandoned, ongoing).
+
+## Recurring Patterns
+Themes that surfaced on more than one day: repeated debugging classes, recurring tradeoffs, friction points, or design tensions.
+
+## Carried-Over / Unfinished Work
+Work still in progress at the end of the range, or open questions that persisted across multiple days.
+
+Daily summaries:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agenthud",
-  "version": "0.9.1",
+  "version": "0.9.3",
   "description": "CLI tool to monitor agent status in real-time. Works with Claude Code, multi-agent workflows, and any AI agent system.",
   "type": "module",
   "main": "dist/index.js",

package/dist/templates/config.yaml

@@ -1,35 +0,0 @@
-# agenthud configuration
-
-width: 100  # between 50~120 
-
-panels:
-  claude:
-    enabled: true
-    interval: 10s
-    max_activities: 20
-    # session_timeout: 60m  # session inactive threshold (default: since midnight)
-
-  git:
-    enabled: true
-    interval: 30s
-    command:
-      branch: git branch --show-current
-      commits: git log --since=midnight --pretty=format:"%h|%aI|%s"
-      stats: git log --since=midnight --numstat --pretty=format:""
-
-  tests:
-    enabled: true
-    interval: manual
-    # command is auto-detected from: vitest, jest, mocha, pytest
-    # all frameworks output JUnit XML to .agenthud/test-results.xml
-    command: npx vitest run --reporter=junit --outputFile=.agenthud/test-results.xml
-
-  project:
-    enabled: true
-    interval: 5m  # doesn't change often
-
-  #docker:
-  #  enabled: true
-  #  command: docker ps --format json
-  #  renderer: list
-  #  interval: manual