lazygocd
~/lazygocd/keybindings

Keybindings

You never need this page memorized: the footer inside the app always shows the keys for the focused pane, and ? opens the full list. This is the same reference, grouped by context.

global
KeyAction
tabCycle focus: groups → history → details → groups
1 2 3Jump straight to the groups, history, or details pane. Same digits the job view uses for its own tabs.
ctrl+gFold group names into the filter. A group-name hit keeps everything under that group, so searching a group name lists the whole group. Off by default, and it works whether the filter box is open or already committed.
escBack one level: details → history → groups; in the groups pane, clears the filter
rRefresh
AConnect / reconnect GoCD (reopens the connect form)
@Connect GitHub (optional, for private-repo commit checks)
?Toggle help
q ctrl+cQuit
movement · any focused list
KeyAction
j/k   ↓/↑Move selection
g/GJump to top / bottom of the focused list
ctrl+d/ctrl+u   pgdn/pgupHalf-page down / up
groups pane
KeyAction
l enter →Expand the selected group, or open the selected pipeline's history
h ←Collapse the selected group
/Fuzzy-filter pipelines by name, across all groups, matched characters highlighted
vOpen your GoCD personalized dashboard views, the same custom tabs from the web UI
VSave the current / filter matches as a new GoCD view
enter (Artifacts)Open or close a folder; on a file, open it in the browser. l/right opens, h/left closes and steps out to the parent
eOpen the current log in your own editor ($VISUAL / $EDITOR); vim and nvim take over the terminal, code and zed open beside it
yCopy: commit SHA (history/details), pipeline or group name (tree), artifact URL (job view)
OOpen the selected pipeline's activity page in the GoCD web UI; on a group header, the GoCD dashboard
TTrigger with environment variables (NAME=VALUE form); plain t triggers as-is
RRerun a failed run: y = failed jobs only, a = the whole stage
fStar / unstar the selected pipeline as a favorite
tTrigger a new run of the selected pipeline (asks to confirm)
pPause / unpause the selected pipeline (asks to confirm)
history pane
KeyAction
tabMove focus into the details pane
escBack to the groups pane
XCancel the currently running stage of the open pipeline (asks to confirm; only offered while a stage is actually active)
oOpen the selected run's commit on GitHub, or the pending deployed...head diff when the latest deploy is behind
OOpen the selected run's value stream map in the GoCD web UI
t p fTrigger / pause / favorite, same as in the groups pane
details pane
KeyAction
enterOpen the selected job's console log
escBack to the history pane
XCancel the currently running stage (asks to confirm)
oOpen the selected run's commit on GitHub
OOpen the selected stage or job's own page in the GoCD web UI
t p fTrigger / pause / favorite, same as elsewhere
job view (console / artifacts / materials)
KeyAction
tab 1-3Switch between the Console, Artifacts, and Materials tabs
/Search the log (inline highlight as you type, enter to confirm)
n/NJump to the next / previous search match
j/kScroll (Console/Materials) or move the selection (Artifacts)
enter oArtifacts tab: open the selected file in your browser
OOpen this job's page in the GoCD web UI, from any tab
g/GJump to top / bottom; G also resumes auto-follow of a live log
rRefresh
q escClose the job view
mouse
InputAction
clickFocus the pane and select the clicked row; clicking an already-selected row opens it
wheelScroll the pane under the cursor, or the console log when it's open
hoverResting on a pipeline row for ~300ms prefetches its history in the background
muscle memory included If you already use vim, k9s, or similar tools, your fingers know most of this: j/k movement, g/G jumps, ctrl+d/ctrl+u paging, / to filter, and esc to back out of anything.
Feature deep-dives Changelog