termpeeklisted

# termpeek Agent CLIs run a full-screen TUI that owns the terminal. They capture subprocess stdout as text, strip escape sequences, and repaint over anything written to the PTY — so an image "displayed" from a tool call is invisible to the user. On Claude Code, `/dev/tty` cannot even be opened from a tool call. termpeek does not fight the TUI. It renders in a place the TUI never repaints: a tmux pane, or a separate terminal window. ## When to use this Reach for termpeek whenever the user should *see* something rather than read a description of it: - after writing or generating an image, chart, diagram, or screenshot - when the user asks "show me", "what does it look like", "preview that" - after downloading or being handed a PDF - to show a code change visually — `termpeek --diff` - for a tweet/X URL the user wants to look at Do not use it for content the agent needs to *reason about*. Reading an image into your own context is the `Read` tool's job; termpeek is for the human's eyes. They solve different problems and are often used together. ## Usage ```bash scripts/termpeek <file|url> # auto-detect type, pick transport, show it scripts/termpeek --diff # working-tree diff, side-by-side scripts/termpeek --diff HEAD~3 # any git diff arguments scripts/termpeek --probe # what this terminal supports ``` Options: | Flag | Meaning | Default | |---|---|---| | `-g, --geometry <WxH>` | size in character cells | `80x40` | | `-p, --protoco