hud-statusline

HUD / Statusline Integration

Guidance for commands and agents to update Claude Code's statusline with real-time Unity workflow state.

Statusline Format

The recommended statusline format for Unity workflows:

[Phase: Execute] [Agent: unity-coder] [Modified: 5 files] [12m]

Fields:

• Phase — current workflow phase: Clarify, Plan, Execute, Verify, Done
• Agent — currently active sub-agent (or "main" if no agent is running)
• Modified — count of unique files edited this session (from session-edits.txt)
• Duration — elapsed session time in minutes

Reading Session State

Statusline data comes from the hook state directory at /tmp/unity-claude-hooks/:

File	Content	Updated By
session-edits.txt	One file path per line (may have duplicates)	track-edits.sh
gateguard-reads.txt	One file path per line	track-reads.sh
session-state.json	Branch, phase, workflow context	session-save.sh
session-start-time	Unix timestamp	session-restore.sh
session-cost.jsonl	One JSON object per tool call	cost-tracker.sh

File Count

EDIT_COUNT=0
if [ -f "/tmp/unity-claude-hooks/session-edits.txt" ]; then
    EDIT_COUNT=$(sort -u "/tmp/unity-claude-hooks/session-edits.txt" | wc -l | tr -d ' ')
fi

Session Duration

DURATION_MINS=0
if [ -f "/tmp/unity-claude-hooks/session-start-time" ]; then
    START=$(cat "/tmp/unity-claude-hooks/session-start-time")
    NOW=$(date +%s)
    DURATION_MINS=$(( (NOW - START) / 60 ))
fi

Integration Points

Commands

Commands with phase gates (like /unity-workflow) should update the statusline at each transition:

Phase 1: Clarify  → statusline: [Phase: Clarify]
Phase 2: Plan     → statusline: [Phase: Plan]
Phase 3: Execute  → statusline: [Phase: Execute] [Agent: unity-coder]
Phase 4: Verify   → statusline: [Phase: Verify] [Agent: unity-verifier]
Done              → statusline: [Phase: Done] [Modified: N files] [Xm]