Skip to content

Rename Pane action is reachable only from the right-click menu — not bindable, not in Command Palette #9351

@psh4607

Description

@psh4607

Pre-submit Checks

Describe the bug

The right-click context menu on a pane title bar includes a Rename pane entry that works as expected. However, the same action is not reachable from any other input surface:

  • Searching rename pane in the Command Palette (⌘P) returns no action results.
  • Searching rename in Settings → Keyboard shortcuts returns only Rename the Current Tab (bound to ⇧⌘R) and Slash command: /rename-tab. There is no Rename Pane (or pane:rename) entry, so the action cannot be bound to a keyboard shortcut.
  • The default keysets manifest at https://github.com/warpdotdev/keysets/blob/main/default-warp-keybindings.yaml exposes 13 pane_group:* actions (add_*, navigate_*, resize_*, toggle_maximize_pane) but no rename action.
  • The slash-command surface only exposes /rename-tab; there is no /rename-pane equivalent.

Since the underlying action is already shipped (the context menu invokes it directly), this looks like a missing registration in the action / keybinding / Command Palette registries rather than a missing feature. Keyboard-driven users currently cannot trigger pane rename without using the mouse.

To reproduce

  1. Open Warp.
  2. Open any tab (single-pane or split via ⌘D / ⇧⌘D).
  3. Right-click on the pane title bar (or click the "⋮" button on it) — the Rename pane entry is present and works as expected.
  4. Open the Command Palette (⌘P) and search for rename pane — no action result appears (only fuzzy file/workflow matches with the document icon).
  5. Open Settings → Keyboard shortcuts and search for rename — only Rename the Current Tab (⇧⌘R) and Slash command: /rename-tab appear. No Rename Pane entry.
  6. Type /rename-pane in the input field — not a recognized slash command (only /rename-tab exists).

Expected behavior

The Rename Pane action should be:

  • registered as a remappable keybinding action (e.g. pane:rename) in the default keysets manifest, with no default key assigned but searchable in Settings → Keyboard shortcuts;
  • discoverable from the Command Palette so it can be invoked via fuzzy search;
  • (optionally) exposed as a /rename-pane slash command, mirroring the existing /rename-tab.

This brings the Rename Pane action in line with Warp's general convention that user-facing actions are reachable from the keybinding registry and Command Palette in addition to a context menu.

Screenshots, videos, and logs

1. Right-click context menu on a pane title bar — Rename pane entry is present and active:

Image

2. Settings → Keyboard shortcuts, searching rename — only Rename the Current Tab (⇧⌘R) and Slash command: /rename-tab appear. No Rename Pane action exists in the registry:

Image

3. Command Palette (⌘P) searching rename — the only action result is Rename the Current Tab (gear icon). The first row (rename, document icon) is a fuzzy file/workflow match, not an action. No Rename Pane action is registered:

Image

Operating system (OS)

macOS

Operating system and version

macOS 26.4

Shell Version

zsh 5.9 (arm64-apple-darwin25.0)

Current Warp version

v0.2026.04.27.15.32.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

Scope is intentionally narrow: this report is only about exposing the already-shipped Rename Pane action through the standard input surfaces (keybinding registry + Command Palette + optional slash command). The broader feature — pane title-bar visualization, persistent pane names, session restoration — is tracked at #1870 (Add optional title to pane) and is out of scope here.

Related issues for context:

Suggested fix scope:

  1. Register a pane:rename action in the keysets manifest (no default keybinding) so it appears in Settings → Keyboard shortcuts.
  2. Wire the same action into the Command Palette search index.
  3. (Optional) Add a /rename-pane slash command mirroring /rename-tab.

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

Ignore

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working.ready-to-implementThe issue is ready for implementation work.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions