Drive interactive flameview terminal sessions and verify UX behavior (columns, filters, navigation, auto-expand). Use when a task requires launching flameview on folded stacks, exercising key bindings, reproducing TUI bugs, or capturing manual UX validation steps.
Launch flameview quickly on representative folded-stack datasets and exercise repeatable key workflows to validate interactive UX behavior after code changes.
Run from any location:
<repo-root>/.codex/skills/flameview-tui-driver/scripts/run_flameview_tui.sh <repo-root> tests/data/large.txt
The script builds flameview if needed and opens the TUI. If no TTY is available it falls back to summarize mode so debugging can continue non-interactively.
Use this sequence after launch to smoke-test the interactive UX:
j / k to move selection.l or Enter to expand a branch.h to collapse.] then [ to adjust minimum total-percent filter.H to toggle hot-only filtering.f to toggle runtime-frame hiding./ then text then Enter to apply search.n / p to jump matches.s to cycle sort modes.z to re-run heuristic auto-expand.q to exit.Run with a specific folded file:
<repo-root>/.codex/skills/flameview-tui-driver/scripts/run_flameview_tui.sh <repo-root> /path/to/file.folded
Run summary mode directly (non-interactive sanity):
cd <repo-root>
./target/debug/flameview --summarize tests/data/small.txt
references/keymap.md for the current key map and status semantics.