d2f26ae9bd
## Description Resolves the keyboard-binding portion of #9351. The Rename Pane action shipped only via the right-click context menu on a pane title bar (\`WorkspaceAction::RenamePane(PaneViewLocator)\`). Because that variant requires an explicit locator, it can't be wired into the keybinding registry, the Command Palette, or Settings → Keyboard shortcuts — keyboard-driven users had no path to the action. This PR mirrors the existing \`RenameActiveTab\` pattern by adding a parameterless \`RenameActivePane\` variant that resolves the active pane at dispatch time and delegates to the existing \`rename_pane\` infrastructure. ## Linked Issue - [x] The linked issue is labeled \`ready-to-spec\` or \`ready-to-implement\`. (#9351 is \`ready-to-implement\`.) Resolves #9351 (binding-registry portion). ## Changes | File | Change | |---|---| | \`app/src/workspace/action.rs\` | New \`RenameActivePane\` variant on \`WorkspaceAction\`; added to \`should_save_app_state_on_action\` (mutates \`pane_configuration\`, parallel to \`RenamePane(locator)\`). | | \`app/src/workspace/view.rs\` | Handler resolves the active tab's pane group, looks up its focused pane id, builds a \`PaneViewLocator\`, and delegates to the existing \`self.rename_pane(locator, ctx)\` path. No new render or persistence code. | | \`app/src/workspace/mod.rs\` | Register \`workspace:rename_active_pane\` (\"Rename the current pane\") as an \`EditableBinding\` under the Settings group, with no default keystroke. Surfaces the action in Settings → Keyboard shortcuts as remappable. | | \`app/src/workspace/action_tests.rs\` | Unit test confirms the new variant participates in \`should_save_app_state_on_action\` alongside \`RenamePane(locator)\`. | ## Scope The issue's three asks are: 1. **Binding registry / Settings → Keyboard shortcuts** — addressed here. ✅ 2. **Command Palette** — out of scope for this PR; \`EditableBinding\` registration alone may already surface it via the existing \`from_editable_lens\` path, but I haven't verified. 3. **Optional \`/rename-pane\` slash command** — out of scope for this PR. (2) and (3) can be follow-ups once (1) lands; keeps the PR atomic. ## Testing - \`action_tests.rs\` covers the persistence contract for the new variant. - I have **not** exercised the binding through Settings → Keyboard shortcuts on a running Warp — this build environment cannot run Warp (no Metal toolchain). CI's MacOS/Linux/Windows lanes will validate compilation, and a maintainer with a working dev build can confirm the new \`workspace:rename_active_pane\` row appears in Settings → Keyboard shortcuts when searching \"rename\". Flagging this honestly so it doesn't get assumed. Once verified, follow-up keysets-manifest registration in [warpdotdev/keysets](https://github.com/warpdotdev/keysets) (out of scope for this repo) would let the action also surface as a default-keyset entry. ## Agent Mode - [ ] Warp Agent Mode - This PR was created via Warp's AI Agent Mode CHANGELOG-IMPROVEMENT: Rename Pane is now reachable from Settings → Keyboard shortcuts as a remappable binding (\`workspace:rename_active_pane\`), in addition to the existing right-click context menu. Thanks @lonexreb!
Website · Code · Agents · Terminal · Drive · Docs · How Warp Works
Note
OpenAI is the founding sponsor of the new, open-source Warp repository, and the new agentic management workflows are powered by GPT models.
About
Warp is an agentic development environment, born out of the terminal. Use Warp's built-in coding agent, or bring your own CLI agent (Claude Code, Codex, Gemini CLI, and others).
Installation
You can download Warp and read our docs for platform-specific instructions.
Warp Contributions Overview Dashboard
Explore build.warp.dev to:
- Watch thousands of Oz agents triage issues, write specs, implement changes, and review PRs
- View top contributors and in-flight features
- Track your own issues with GitHub sign-in
- Click into active agent sessions in a web-compiled Warp terminal
Licensing
Warp's UI framework (the warpui_core and warpui crates) are licensed under the MIT license.
The rest of the code in this repository is licensed under the AGPL v3.
Open Source & Contributing
Warp's client codebase is open source and lives in this repository. We welcome community contributions and have designed a lightweight workflow to help new contributors get started. For the full contribution flow, read our CONTRIBUTING.md guide.
Tip
Chat with contributors and the Warp team in the
#oss-contributorsSlack channel — a good place for ad-hoc questions, design discussion, and pairing with maintainers. New here? Join the Warp Slack community first, then jump into#oss-contributors.
Maintaining a popular open-source project? Apply for Oz credits to bring agentic workflows like issue triage, PR review, and community management to your repo.
Issue to PR
Before filing, search existing issues for your bug or feature request. If nothing exists, file an issue using our templates. Security vulnerabilities should be reported privately as described in CONTRIBUTING.md.
Once filed, a Warp maintainer reviews the issue and may apply a readiness label: ready-to-spec signals the design is open for contributors to spec out, and ready-to-implement signals the design is settled and code PRs are welcome. Anyone can pick up a labeled issue — mention @oss-maintainers on an issue if you'd like it considered for a readiness label.
Building the Repo Locally
To build and run Warp from source:
./script/bootstrap # platform-specific setup
./script/run # build and run Warp
./script/presubmit # fmt, clippy, and tests
See WARP.md for the full engineering guide, including coding style, testing, and platform-specific notes.
Joining the Team
Interested in joining the team? See our open roles.
Support and Questions
- See our docs for a comprehensive guide to Warp's features.
- Join our Slack Community to connect with other users and get help from the Warp team — contributors hang out in
#oss-contributors. - Try our Preview build to test the latest experimental features.
- Mention @oss-maintainers on any issue to escalate to the team — for example, if you encounter problems with the automated agents.
Code of Conduct
We ask everyone to be respectful and empathetic. Warp follows the Code of Conduct. To report violations, email warp-coc at warp.dev.
Open Source Dependencies
We'd like to call out a few of the open source dependencies that have helped Warp to get off the ground: