tui-verify-change

Verify Warp TUI changes by running the binary and reading the rendered screen via tmux.

64.7k|5.5k|Updated Jul 8, 2021
One-click install
npx skills add https://github.com/warpdotdev/warp --skill tui-verify-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tui-verify-change
Source: https://github.com/warpdotdev/warp/tree/main/.agents/skills/tui-verify-change
Command: npx skills add https://github.com/warpdotdev/warp --skill tui-verify-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you change Warp's headless TUI front-end (crates/warp_tui or the cell-grid elements in warpui_core), compiling and unit tests alone don't confirm what users actually see. This Skill runs the TUI in a real terminal and reads back the actual rendered screen so you can confirm the on-screen result of UI, rendering, input, or behavior changes.

Core Features & Use Cases

  • Live screen verification: Build warp-tui-oss, run it in a tmux pane, drive it with tmux send-keys, and read the rendered frame back with tmux capture-pane, with a fallback to script or direct runs when tmux is unavailable.
  • Local and cloud login paths: Use ./script/run-tui with interactive device-auth locally, or a WARP_API_KEY environment variable for non-interactive login on headless cloud runners.
  • Screenshot and video evidence: Record sessions with asciinema, render with agg, and transcode to H.264 MP4 with ffmpeg, then attach stills and clips as conversation artifacts for PR evidence.
  • Use Case: You changed the login placeholder text in crates/warp_tui/src/ui.rs. Rebuild, relaunch the tmux session, and capture-pane shows the new string rendered on screen, confirming the change end-to-end.

Quick Start

Verify my TUI change by building warp-tui-oss, running it in a tmux session, and capturing the rendered screen to confirm the new output appears.

Frequently Asked Questions about tui-verify-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a TUI change in a terminal application?

Build the warp-tui-oss binary, launch it in a detached tmux session with explicit dimensions, then use tmux capture-pane to read the rendered screen as text. Drive interactions with tmux send-keys and capture again to confirm the change appears on screen.

How to capture terminal output as a screenshot or video?

Record the TUI's PTY session with asciinema inside tmux, render the cast to GIF with agg, then transcode to an H.264 yuv420p MP4 with ffmpeg. Extract a still frame with ffmpeg at a mid-recording timestamp while the surface is displayed.

Can I run terminal UI verification without tmux installed?

Yes, tmux is preferred but not required. Locally, run ./script/run-tui directly in a real terminal and read the output. In cloud environments, wrap the binary with the script command to capture output to a log file, or install tmux via apt if available.

How do I log in to a TUI app on a headless cloud runner?

Set WARP_API_KEY in the environment before launching any TUI channel binary, which authenticates without the browser device-auth flow. Never echo or inline the key value; rely on the inherited environment variable so the secret stays hidden.

Why does the TUI exit with code 101 right after starting?

Check the log at ~/.local/state/warp-terminal-tui/oz/warp-tui.log first. A known cause is a debug-only binding-validation panic in the keymap matcher; building with --release compiles out the validator, or you can poll capture-pane immediately after launch to grab the first frame.