[sharanry]

"Regenerate title" can only be triggered from the thread context menu, so it can't be bound to a key: KeybindingCommand is a closed list and nothing in it covers title regeneration. Closes #33983.

Added a thread.regenerateTitle thread keybinding command. Its handler in useThreadLifecycle does what the menu item does: it sends updateMetadata with regenerateTitle: true for the focused thread. It applies the same guards as thread.pin/thread.settle: it needs operate scope and loaded server config, it does nothing while a regeneration is already in flight, and it shows a toast if it fails. It has no default shortcut, so default behavior doesn't change. It shows up in Settings → Keybindings like the other unbound commands (for example thread.stop), and I added a sentence for it in docs/user/keybindings.md.

Surfaces: web and desktop share this handler. Mobile has no keybindings, and agents already have regenerate_title through the thread-metadata MCP tool. No server or contract-shape changes beyond the enum entry.

Verification: vp run check:changed passed format, lint, knip, typecheck (37 packages), the react compiler check, and 2 of 3 tests. The remaining browser test file couldn't launch locally because Playwright's headless Chromium isn't installed on this machine.

Done with Claude Code (Claude Opus 5.5).

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Approved at 3e5e222

Macroscope's review found this PR approvable — Adds an optional shortcut for the existing thread-title regeneration action, with permission and in-progress guards. No default shortcut or existing product behavior changes.

Notes:

• Code review disabled. Approvability was decided on eligibility alone.

^{You can add or adjust custom eligibility rules. Learn more.}