Terminal UI
The er Terminal UI
er is a single, dependency-free binary that renders a fast, keyboard-driven review UI in your
terminal. It starts in under a second and is designed to sit in a split pane next to an AI coding assistant. This
page covers what is specific to the terminal app; the shared concepts live under
Core Concepts.
Launching
Run er from inside any git repository. Common invocations:
er # review the current branch diff
er --pr 42 # open a GitHub PR by number
er https://github.com/owner/repo/pull/42 # open a PR by URL
er ~/projects/api ~/projects/frontend # open multiple repos as tabs
er --filter '+*.rs,-*.lock' # pre-filter the file list
er --target release/v2 # diff against a specific base branch
| Flag / argument | Effect |
|---|---|
--pr <n> | Open pull request n in the current repo |
| a PR URL | Open that pull request — you must be inside a clone of that repo (use --remote otherwise) |
| one or more paths | Open each repository / worktree as a tab |
--filter <expr> | Apply a filter at startup |
--remote | Review a PR from any directory, without a local clone (requires gh) |
--target <branch> | Override the detected base branch (useful for stacked branches) |
--help | Show all options |
er renders via crossterm/ratatui and needs a real terminal (such as a tmux
pane), not a headless pipe.
The layout
The screen has a top bar, three columns, and a bottom bar.
er terminal UI — top bar with diff modes and PR status, the file list, a syntax-highlighted diff with inline GitHub comments (cyan), AI findings (orange) and private questions (yellow), and the PR context panel on the right.| Region | Shows |
|---|---|
| Top bar | The diff modes (with the active one highlighted), the detected PR, the reviewed count, AI status badges, and the watch indicator. |
| Left — file list | Every changed file with a status dot, AI risk indicator, and comment/finding badges. In history mode this becomes the commit list. |
| Center — diff | The unified diff with syntax highlighting, inline comments and findings, and a sticky file-path header. |
| Right — context panel | File details, the AI summary, the PR overview (CI checks and reviewers), or the agent log depending on context. |
| Bottom bar | Key hints (configurable) and comment input when you are typing a note. |
Working beside an AI assistant
The intended workflow is a split terminal: Claude Code (or your tool of choice) on one side, er on the
other, in tmux, Ghostty, or any terminal that splits panes. As the assistant edits, stages, and commits,
er's watch mode keeps the diff live. Open
the AI Hub with a and run a review — findings appear in er automatically.
Layers and panels: dialing AI density up and down
Inline annotations are organized as toggleable layers: A shows or hides AI findings, C GitHub comments, Q questions and notes, and X hides resolved items. The right-hand context panel cycles with p (backward with P) through file details, the AI summary with the risk breakdown, the PR overview, and the agent log. Together they are the terminal's way of dialing review context up and down — from a plain diff to a fully annotated one. See AI Review.
Hubs: everything else is one key away
Less frequent actions live in modal hubs: a opens the AI Hub (reviews, triage, experts, professor), g the Git hub (push, stage, comment sync), v the Verify hub (tests, linters, and other configured commands), y the copy hub, o the open hub (repositories and worktrees), , the settings hub, and ? the help hub, which lists the keys grouped by area.
Stacked PRs
On a branch that belongs to a stack, the open hub
(o) grows a ── Stack ── section: one row per layer, ordered top-of-stack first,
each showing its branch name and PR number, with the layer's state (open, merged,
queued, needs rebase) and the trunk closing the list. Enter opens
that PR for review, b opens it on GitHub.
The list comes from the gh stack extension
(gh extension install github/gh-stack); gh stack view runs on a background
thread, so the hub opens instantly with a loading row. When the extension isn't installed, or the
current branch isn't part of a stack, the section explains why instead of going blank.
Syntax highlighting
The terminal uses syntect for highlighting, with a content-hash cache so unchanged lines are never
re-highlighted between frames. The active theme (set in configuration) selects a
matching highlight palette.
Debug mode
Run with ER_DEBUG=1 to write a debug log and show the memory budget in the status bar:
ER_DEBUG=1 er # writes /tmp/er_debug.log (overwritten each git diff)
Ready to memorize the keyboard? The Keybinding Reference is the complete, grouped list of every key.