claude-code - 💡(How to fix) Fix [FEATURE] Configurable keymap for agent view navigation (vim preset) [1 comments, 2 participants]

Preflight Checklist

• Searched existing requests — no existing issue covers agent-view keymap configuration.
• This is a single feature request.

Problem Statement

Agent view (claude agents, v2.1.139 Research Preview) navigation is currently hardcoded to arrow keys plus a fixed set of Ctrl/letter shortcuts. Users with vim muscle memory — and users on keyboards/layouts where the defaults are awkward — have no way to remap. Hardcoding a "vim mode" would just trade one fixed scheme for another.

Proposed Solution

Introduce a configurable keymap for the agent view in /config (e.g. agentView.keymap), with named presets and per-action overrides:

• default — current arrow-key scheme.
• vim — j/k move, gg/G top/bottom, Ctrl+d/u half-page, / search-filter, x stop/delete, Enter attach.
• A per-action override map so users can bind any action to any key, regardless of preset.

Presets are the easy on-ramp; the override map is the real ask — it future-proofs against layout conflicts and lets non-vim users fix awkward bindings too.

Rationale

The view is iterating fast (5 follow-up releases in the week after launch) and is already accumulating bindings (Ctrl+S, Ctrl+R, Ctrl+X, ?). Locking them in hardcoded makes every future binding a potential conflict. A keymap config makes the surface extensible and accessible without privileging one editor's conventions.

Priority

Medium.

Feature Category

TUI / agent view / keybindings

Use Case Example

A vim user sets agentView.keymap: vim and navigates the session list with j/k, jumps to the bottom with G, and filters with /needs input — no reach for the arrow keys. A Dvorak user instead remaps just the two motion keys via the override map.

Suggested Labels

enhancement, area:agent-view, keybindings