~/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

Key	Action
`tab`	Cycle focus: groups → history → details → groups
`esc`	Back one level: details → history → groups; in the groups pane, clears the filter
`r`	Refresh
`A`	Connect / reconnect GoCD (reopens the connect form)
`@`	Connect GitHub (optional, for private-repo commit checks)
`?`	Toggle help
`q` `ctrl`+`c`	Quit

movement · any focused list

Key	Action
`j`/`k` `↓`/`↑`	Move selection
`g`/`G`	Jump to top / bottom of the focused list
`ctrl`+`d`/`ctrl`+`u` `pgdn`/`pgup`	Half-page down / up

groups pane

Key	Action
`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
`v`	Open your GoCD personalized dashboard views, the same custom tabs from the web UI
`V`	Save the current `/` filter matches as a new GoCD view
`y`	Copy: commit SHA (history/details), pipeline or group name (tree), artifact URL (job view)
`T`	Trigger with environment variables (NAME=VALUE form); plain `t` triggers as-is
`R`	Rerun a failed run: `y` = failed jobs only, `a` = the whole stage
`f`	Star / unstar the selected pipeline as a favorite
`t`	Trigger a new run of the selected pipeline (asks to confirm)
`p`	Pause / unpause the selected pipeline (asks to confirm)

history pane

Key	Action
`tab`	Move focus into the details pane
`esc`	Back to the groups pane
`X`	Cancel the currently running stage of the open pipeline (asks to confirm; only offered while a stage is actually active)
`o`	Open the selected run's commit on GitHub, or the pending deployed...head diff when the latest deploy is behind
`t` `p` `f`	Trigger / pause / favorite, same as in the groups pane

details pane

Key	Action
`enter`	Open the selected job's console log
`esc`	Back to the history pane
`X`	Cancel the currently running stage (asks to confirm)
`o`	Open the selected run's commit on GitHub
`t` `p` `f`	Trigger / pause / favorite, same as elsewhere

job view (console / artifacts / materials)

Key	Action
`tab` `1`-`3`	Switch between the Console, Artifacts, and Materials tabs
`/`	Search the log (inline highlight as you type, `enter` to confirm)
`n`/`N`	Jump to the next / previous search match
`j`/`k`	Scroll (Console/Materials) or move the selection (Artifacts)
`enter` `o`	Artifacts tab: open the selected file in your browser
`g`/`G`	Jump to top / bottom; `G` also resumes auto-follow of a live log
`r`	Refresh
`q` `esc`	Close the job view

mouse

Input	Action
`click`	Focus the pane and select the clicked row; clicking an already-selected row opens it
`wheel`	Scroll the pane under the cursor, or the console log when it's open
`hover`	Resting 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