Feature: Session summary element for Claude Code status line

[donghoon-lee-mrt]

Feature Request

Description

Add a new HUD element that displays a brief summary (under 20 characters) of what the user is currently doing in the session, derived from the conversation transcript.

Motivation

When working with multiple Claude Code sessions or glancing at the status line, it's hard to tell at a glance what each session is about. A short, auto-generated summary like fixing auth bug or adding API tests would make it much easier to identify and switch between sessions.

Proposed Behavior

• Analyze the current session's conversation transcript
• Generate a concise summary of the ongoing task (< 20 characters)
• Display it as a new element in the HUD status line
• Update dynamically as the conversation topic shifts

Generation Rules

1. Initial generation: Only after 10+ conversation turns have accumulated
2. Update frequency: Regenerate every 10 additional turns (not on every render)
3. Generation method: Use claude -p command to summarize the transcript
4. Cache: Store the generated summary and the turn count at generation time, only regenerate when currentTurns - lastGeneratedTurns >= 10

Example Output

[OMC#1.2.3] 5h:45% | ctx:[████░░]67% | 📝 fixing auth bug

Implementation Ideas

• New element file: src/hud/elements/session-summary.ts
• Parse transcript (already available via transcript_path in stdin) to count turns
• Use claude -p to generate summary when turn threshold is met
• Cache summary in HUD state (hud-state.json) with lastSummaryTurnCount and summary fields
• Add sessionSummary toggle to HudElementConfig
• Add to presets (probably focused and full)

Configuration

{
  "omcHud": {
    "elements": {
      "sessionSummary": true
    }
  }
}

🤖 Generated with Claude Code

[Yeachan-Heo]

Thanks for the feature request! This is an interesting idea — a short session summary in the statusline would definitely help with multi-session workflows.

A few considerations:

• The transcript analysis would need to be lightweight enough not to add latency to every HUD render
• The 20-char limit is a good constraint — keeps it scannable
• Would need to decide on update frequency (on every message? periodic?)

We'll keep this on the radar. PRs welcome if you want to take a crack at it!

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[Yeachan-Heo]

Resolved by #1687 (merged to dev).

—
[repo owner's gaebal-gajae (clawdbot) 🦞]