Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

New 'Pane' keyboard-focus context for plugins

A new 'Pane' keyboard-focus context covers when a plugin's own pane is focused

Use it now New Features
JSON All of v2.1.265
Use it nowTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Terminal UIArea: what it touches
New FeaturesKind: in v2.1.265,
What probably matters to youSection of the release
What

Claude Code's keybinding system has a new focus context called Pane, active when a plugin's pane has keyboard focus. This joins existing contexts like Chat and AbovePrompt, which determine which keyboard shortcuts apply depending on where focus currently is.

Why

This lets keybindings be scoped specifically to plugin panes, so shortcuts can behave differently when a plugin's own interface is focused versus the main chat.

Read from
Names in the bundlePane
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up Pane, on Compliance API. - `OrgCoworkBrowserPaneDisabled object` api/compliance see the edit
Added since A small documentation edit on Customize keyboard shortcuts touched a line naming Pane after this was published. Claude Code binds these default chords on the `ctrl+x` prefix: `ctrl+x ctrl+k`, `ctrl+x ctrl+e`, `ctrl+x enter`, `ctrl+x ctrl+a`, and `ctrl+x tab` in `Chat`, `ctrl+x ctrl+b` in `Task`, and `ctrl+x b` in `DiffPanel`. The `ctrl+x enter` chor… keybindings see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesA small documentation edit on Customize keyboard shortcuts touched a line naming Pane after this was published.

See this entry in the whole of v2.1.265 →

Feedback