What
Plugin UI components used when rendering plugin panes gained new props:
Buttonnow acceptsaction(must be one of the engine's existing keybinding actions, such asapp:cycleDiffBaseorapp:diffFileListDown; engine-only keys likectrl+c/ctrl+dstill can't be rebound), plus adimColorboolean.Button,Input, andSelectall gain anautoFocusprop.
Why
Plugin authors building custom UI panes can now make a button trigger an existing app action, dim button text, and have a component automatically receive focus when it appears, without writing custom focus-handling logic.
Names in the bundleautoFocus
Documented inclaude-code/plugins/mods/interface
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 autoFocus, on Draw in the interface with a mod.
* **`autoFocus`**: to choose which control has the focus when the pane opens, add `autoFocus: true` to it. The prop accepts only `true`, so omit it on the other controls.plugins/mods/interface see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up autoFocus, on Draw in the interface with a mod.