Skip to content

Open-source Grok Bot alternative for named AI teammates. Local-first desktop, web, and mobile clients with per-bot tools, instructions, and memory. Independent fork of T3 Code.

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

Utkarsh Patil239ef1c54df2
diff --git a/apps/web/src/components/SidebarV2.tsx b/apps/web/src/components/SidebarV2.tsx
index 409d6bef9..81d883508 100644
--- a/apps/web/src/components/SidebarV2.tsx
+++ b/apps/web/src/components/SidebarV2.tsx
@@ -2816,11 +2816,13 @@ export default function SidebarV2() {
openCommandPalette({ open: "new-thread-in" });
}, [isMobile, newThreadContext, projectGroups.length, setOpenMobile]);
- // Same resolution as v1: prefer the local-thread binding, fall back to
- // chat.new, no platform gating — web users have working shortcuts too.
+ // The button mirrors chat.new: in multi-project setups both route through
+ // the command palette's "New thread in..." picker, and in single-project
+ // setups both create immediately. chat.newLocal always creates directly, so
+ // it is only a correct label when chat.new is unbound.
const newThreadShortcutLabel =
- shortcutLabelForCommand(keybindings, "chat.newLocal") ??
- shortcutLabelForCommand(keybindings, "chat.new");
+ shortcutLabelForCommand(keybindings, "chat.new") ??
+ shortcutLabelForCommand(keybindings, "chat.newLocal");
return (
<>
<SidebarChromeHeader isElectron={isElectron} />