Problem
The status bar is the primary discoverability mechanism for keybindings, but it currently only covers the most important actions. Users on less-common views (routers, security groups, load balancers) may not know what actions are available without opening the help overlay.
Proposed Solution
- Audit all views and ensure the status bar shows context-relevant keybinding hints
- Prioritize the most common actions per view (space is limited)
- Consider a "more..." indicator that tells users to press
? for the full list
Priority
Medium — this is the main way users learn the tool organically.
Context
Identified during features & usability review.
Problem
The status bar is the primary discoverability mechanism for keybindings, but it currently only covers the most important actions. Users on less-common views (routers, security groups, load balancers) may not know what actions are available without opening the help overlay.
Proposed Solution
?for the full listPriority
Medium — this is the main way users learn the tool organically.
Context
Identified during features & usability review.