Pre-submit Checks

• I have searched Warp feature requests and there are no duplicates
• I have searched Warp docs and my feature is not there

Describe the solution you'd like?

Summary

As a Neovim and tmux user who relies entirely on keyboard navigation, I find several friction points in Warp's editor and file explorer that make it difficult to integrate into a keyboard-driven workflow. The gaps span file tree navigation, buffer switching, visual feedback, and LSP interaction.

Problem

1. File explorer focus requires toggling: When the file tree (project explorer) is open but not focused, there is no dedicated keybinding to shift focus into it. I have to toggle it off and back on to regain focus, which breaks flow.
2. No file preview in explorer: There is no way to preview a file's contents from the file tree without fully opening it.
3. Weak visual feedback for active panels: When I activate the code editor, there is sometimes no clear visual indicator that it is the active pane. The active-state indicator for terminal panels is also hard to discern.
4. No efficient buffer navigation: When multiple files are open in the code editor, there is no quick keyboard-driven way to cycle or switch between open buffers/tabs.
5. LSP features require mouse interaction: Warp already provides LSP-powered hover, go-to-definition, find references, rename, and diagnostics, but these are primarily mouse-driven (CMD-click / CTRL-click). For a Vim-centric workflow, keyboard equivalents are essential.
6. No custom Vim keybindings for LSP: Warp's code editor supports Vim keybindings, but the documentation states only default bindings are supported (with one exception). This means common IDE-Vim mappings like gd (go to definition), K (hover), gr (find references), and grr (rename) cannot be configured.
7. No plugin extensibility: There is no plugin system to allow users to add custom editor behavior, keybindings, or integrations.

Expected behavior

• A dedicated keybinding to focus the file tree (and return focus to the editor/terminal) without toggling visibility.
• File preview in the explorer (e.g., via keyboard selection or quick preview pane).
• Stronger, unambiguous visual indicators for whichever pane (editor or terminal) is currently active.
• Keyboard shortcuts to switch between open editor buffers (e.g., gt/gT style or numbered tabs).
• Full keyboard access to LSP features: gd for go-to-definition, K for hover/documentation, gr for find references, grr for rename, etc.
• Ability to customize Vim keybindings in the code editor beyond the current default set.
• A plugin architecture to extend editor and terminal behavior.

Actual behavior

• File tree focus requires closing and reopening the panel.
• Files in the tree open immediately; no preview mode exists.
• Active panel state is sometimes visually subtle or missing.
• Buffer switching requires using the mouse or cycling through all panes.
• LSP features like go-to-definition and hover are only accessible via mouse modifier + click.
• Vim mode in the code editor does not support custom keybindings for LSP actions.
• No plugin system is available.

Reproduction steps or desired workflow

1. Open a project in Warp and open the file tree with CMD-\.
2. Open a file in the code editor, then click back into the terminal.
3. Attempt to return focus to the file tree via keyboard — no direct binding exists; must toggle CMD-\ twice.
4. Open multiple files in the code editor.
5. Try to switch between open editor buffers using only the keyboard — no efficient binding exists.
6. In a file with LSP enabled, place cursor on a symbol and press gd — nothing happens (expected: jump to definition).
7. Place cursor on a symbol and press K — nothing happens (expected: hover tooltip).

Artifacts

None attached.

Warp version

Unknown

Operating system

macOS

Possible source references

• File Tree docs: describes opening the tree via CMD-\ and assigning custom shortcuts in Settings, but does not mention focus or preview behavior.
• LSP docs: documents hover, go-to-definition, find references, and format-on-save, but notes these are triggered via CMD-click / CTRL-click.
• Vim Keybindings docs: states "At the moment, Warp only supports default Vim keybindings" with one exception for exiting insert mode.

Is your feature request related to a problem? Please describe.

No response

Additional context

No response

Operating system (OS)

macOS

How important is this feature to you?

5 (Can't work without it!)

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None