Summary

When --stdout is passed, the export command (E key or :clip/:export) prints the review markdown to stdout and exits, instead of copying to the clipboard. This is useful for piping to other tools or redirecting to a file.

Motivation

This enables running tuicr programmatically from AI coding assistants like Claude Code, leveraging tmux to open a split pane for the interactive review while capturing the exported comments via stdout. I'll be raising a follow-up PR with a complementary Claude Code skill that uses this feature.

First of all, kudos on this tool - it's incredibly handy for reviewing AI-generated diffs in a structured way. The GitHub PR-style interface makes it easy to leave contextual comments, and the vim-like keybindings feel natural. This --stdout flag is a small addition that opens up powerful automation possibilities.

Changes

• Add CliArgs struct and parse_cli_args() for CLI argument handling
• Add output_to_stdout and pending_stdout_output fields to App
• Extract generate_export_content() from export_to_clipboard()
• Render TUI to /dev/tty when --stdout is used (keeps stdout clean for capture)
• Skip the "Copy to clipboard?" confirmation dialog when --stdout is set
• Print pending output after TUI cleanup

Usage

# Export review to stdout instead of clipboard
tuicr --stdout > review.md

# Pipe to another tool
tuicr --stdout | pbcopy

# Use from tmux (e.g., from an AI assistant)
tmux split-window -h "tuicr --stdout > /tmp/review.md"

Test plan

• tuicr --help shows the new --stdout option
• Running with --stdout, adding comments, and pressing E outputs markdown to stdout
• TUI renders correctly (to /dev/tty) while stdout captures only the export
• Without --stdout, behavior unchanged (copies to clipboard)

🤖 Generated with Claude Code