Skip to content

feat(plugin): redesign CodingBuddy status bar as a two-line workflow snapshot #1320

Description

@JeremyDev87

Background

CodingBuddy already installs a custom Claude Code statusLine script via /Users/pjw/workspace/codingbuddy/packages/claude-code-plugin/hooks/session-start.py.

However, the current status line still has several product gaps:

  • it relies on estimated cost/duration instead of exact Claude Code telemetry where available
  • it underuses Claude Code stdin fields such as exact cost, duration, rate limits, worktree, and agent info
  • it exposes only a thin workflow snapshot from CodingBuddy state
  • its second line is not yet a compact, intuitive, badge-based summary of what the workflow is doing
  • the status bar and the live spinner/statusMessage surface are not clearly separated in product intent

The desired behavior is:

  • Status bar: a stable two-line workflow snapshot for Claude Code terminal usage
  • Spinner / statusMessage: the more transient live activity surface

Claude Code supports multi-line status lines, so CodingBuddy can intentionally use two lines rather than trying to compress everything into one.

Goal

Redesign the CodingBuddy status bar into a reliable two-line snapshot with:

  • exact Claude Code telemetry on the first line
  • a compact badge-based workflow strip on the second line
  • clearer state ownership between stdin telemetry, HUD state, and live hook activity

Scope

In scope:

  • codingbuddy-hud.py data sourcing and rendering
  • HUD state schema and updates
  • hook wiring needed to keep the workflow snapshot useful
  • badge design for the second line
  • documentation of the status bar model and multiline support

Out of scope:

  • TUI HUD redesign
  • replacing PreToolUse spinner/statusMessage behavior
  • unrelated command namespace work

Proposed UX

Line 1 should read like a stable session summary, for example:

◕‿◕ CB | PLAN | technical-planner | Opus | 18% ctx | $0.015 | 4m

Line 2 should read like compact workflow badges, for example:

[◮ secu] [🔍 auth] [⚠1]

The intended interpretation is:

  • line 1 = core telemetry and session state
  • line 2 = CodingBuddy workflow meaning

Acceptance criteria

This parent issue is complete when all of the following are true:

  • the first line prefers exact Claude Code stdin telemetry over internal estimates when available
  • the second line renders as compact badge-based workflow state rather than a plain sentence dump
  • HUD state can store enough workflow information to power the second line
  • the relevant hooks keep HUD state fresh enough to make the snapshot useful
  • docs explain the two-line model and the difference between stable status bar state vs live spinner/statusMessage activity

Sub-issues

Recommended order

  1. feat(plugin): use exact Claude Code stdin telemetry in codingbuddy-hud.py #1325
  2. feat(plugin): extend HUD state schema for richer workflow snapshots #1326
  3. feat(plugin): wire hook-driven workflow state updates into the HUD snapshot #1324
  4. feat(plugin): add a badge-based second line renderer for the CodingBuddy status bar #1323
  5. docs(plugin): document the two-line status bar model and its data-source priorities #1322

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Priority 1: First Impressionfeatparent-issue하위 이슈를 포함하는 상위 이슈pluginpackages/claude-code-pluginpriority:mediumMedium prioritywow-experiencePlugin Wow Experience Design

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions