workflow-monitor

workflow-monitor

Overview

A live, read-only, Windows-native Textual cockpit for Claude Code Workflow (ultracode) runs. It surfaces the one signal the native /workflows view and the old per-agent tailers under-use: the live-flushed telemetry manifest ~/.claude/projects/<proj>/<sess>/workflows/wf_<id>.json (re-written ~0s after every agent progress event), which already carries per-agent label (the human lens name), phase, model, state, tokens, tool activity, and prompt/result previews — for the whole fan-out, across every session/project.

Run it

pip install textual rich          # one-time (textual is the only non-stdlib dep)
python workflow_monitor.py        # the interactive whole-fleet cockpit
python workflow_run.py            # a plain-text one-shot fleet board (no TUI) — quick check / CI-friendly

Cockpit: left = filter + status chips + a run → phase → agent tree (glyph · lens · model · tokens · last-tool; ↻ retry, STALL Ns when idle); right = the selected agent's Task (its prompt), a live Feed (transcript tail), and Result (headline + clean output). Keys: q quit · f live-follow · r refresh. It never writes any .claude file and polls O(changed) so it stays snappy across hundreds of runs.

How it works

workflow_run.py is the shared, dependency-light parser (manifest + journal + transcripts + FleetPoller O(changed) polling); the recall-workflow-agent skill shares this same core. Output/status come from the authoritative journal result / started events, not mtime guessing.

Export a run (e / wfmon export)

Caveat (important)