Linear — triage inbox to keyboard command action
Triage starts in a split master-detail inbox where single-key verbs sit directly over the issue body. Pressing ⌘K opens a 640px centered command palette that morphs in place into a sub-menu with breadcrumb context when assigning a cycle or owner.
Step 1 of 3
Linear — Triage Inbox & Split Inspector- grid/layoutTwo-pane master-detail split (320px queue list on the left, fluid issue document on the right) separated by a 1px solid rgba(255,255,255,0.07) hairline with zero outer card margins.
- component patternTriage action bar pins four single-keystroke verbs (Accept [1], Duplicate [2], Snooze [H], Decline [⌫]) directly above the issue description so the cursor never travels to a corner.
Step 2 of 3
Linear — Command Menu (⌘K) Filtered State- component pattern640px centered command palette anchored 18vh from the top viewport edge so result rows expand downward without shifting the input field's vertical coordinates.
- motion/interactionEach result row right-aligns its two-key chord badge (e.g. G then I) in 11px tabular monospace; typing filters the list in <16ms with zero skeleton flash.
Step 3 of 3
Linear — Sub-menu Assignee & Cycle Picker- component patternSelecting an action morphs the command palette in place: the parent issue ID collapses into a 12px breadcrumb chip above the input while the list swaps to cycle capacity bars.
- grid/layoutEach assignee row pairs a 20px avatar, full name, and active workload count in a single 36px-tall row — density tuned so 10 teammates fit without scrolling.
Agents get the same order from get_reference: any screen's reply names the flow and every step in it.