authorgravatar for 73941998+UtkarshUsername@users.noreply.github.comUtkarsh Patil <73941998+UtkarshUsername@users.noreply.github.com> 2026-08-07 16:24:36+05:30
committergravatar for noreply@github.comGitHub <noreply@github.com> 2026-08-07 12:54:36+02:00
log239ef1c54df2f657912ccb5b8e25193d49d90417
treef4a8624ff921984aaf0e668f51badbe89874c0f0
parent61b51ae0e343afc42ba0424d4d74b4f9a216d620
signature Signed by PGP key B5690EEEBB952194

fix(web): show the correctly matching shortcut in new thread button's tooltip (#5594)

1 files changed, 6 insertions(+), 4 deletions(-)

apps/web/src/components/SidebarV2.tsx+6-4
......@@ -2816,11 +2816,13 @@ export default function SidebarV2() {
28162816 openCommandPalette({ open: "new-thread-in" });
28172817 }, [isMobile, newThreadContext, projectGroups.length, setOpenMobile]);
28182818
2819 // Same resolution as v1: prefer the local-thread binding, fall back to
2820 // chat.new, no platform gating — web users have working shortcuts too.
2819 // The button mirrors chat.new: in multi-project setups both route through
2820 // the command palette's "New thread in..." picker, and in single-project
2821 // setups both create immediately. chat.newLocal always creates directly, so
2822 // it is only a correct label when chat.new is unbound.
28212823 const newThreadShortcutLabel =
2822 shortcutLabelForCommand(keybindings, "chat.newLocal") ??
2823 shortcutLabelForCommand(keybindings, "chat.new");
2824 shortcutLabelForCommand(keybindings, "chat.new") ??
2825 shortcutLabelForCommand(keybindings, "chat.newLocal");
28242826 return (
28252827 <>
28262828 <SidebarChromeHeader isElectron={isElectron} />