Repository navigation
Description
What happened
A new user (fresh install of the desktop app) wanted to switch a new thread to a different project. They clicked the project name in the top-bar breadcrumb (my-portfolio / New thread) and nothing visible happened, so they concluded project switching was broken. The only project list they could find was the sidebar filter.
The actual project picker is the project name inside the centre heading, "What should we build in my-portfolio?". The user did not recognise it as clickable until it was explicitly pointed out.
Diagnosis
This is not a functional bug. Both controls work as coded, but their affordances are swapped:
- The top-bar breadcrumb project name looks like a switcher but is a "New thread in " button.
apps/web/src/components/chat/ChatHeader.tsx(around lines 290-307) wires it toonNewThreadInProject. When you are already on an empty new thread in that project, clicking it changes nothing on screen. The only hint is a hover tooltip ("New thread in my-portfolio"). This is unchanged onmainas of 2026-10-30. - The real project picker in the draft hero has no visual affordance. In
apps/web/src/components/chat/DraftHeroHeadline.tsx, the project name is aComboboxTriggerrendered asInlineButton tone="picker". Inapps/web/src/components/ui/button.tsx:108-109, that tone only adds an underline while the popup is open (data-popup-open:underline). At rest it reads as slightly bolder heading text: no underline, chevron, or outline.
As a result, a first-time user clicks the thing that looks interactive (breadcrumb), sees nothing happen, and never discovers the thing that is interactive (heading).
Suggestions (any one would have prevented this):
- Make the breadcrumb project name open the same project picker, or at least do so when the current thread is an empty draft.
- Give the hero project name a resting affordance, such as a chevron, a dotted underline, or a hover background.
- If the breadcrumb must stay "new thread", give it a visual cue such as a
+icon so it doesn't read as a picker.
Steps to reproduce
- Install the desktop app and add at least two projects.
- Open a new thread in project A. The top bar shows
A / New thread. - Click
Ain the top bar. Expected: a project list. Actual: no visible change (a new thread in A is "opened" again). - Note that "What should we build in A?" gives no indication that
Ais clickable. Clicking it does open the "Search projects..." picker.
Version
0.1.5 (desktop app and local server)
Environment
macOS 27.0 (Darwin 27.0.0, arm64), Node v26.12.1, desktop app "T3 Code (Beta)" 0.1.5 against the local server
Evidence
# ChatHeader.tsx (v0.1.5 and main): breadcrumb project button
aria-label={`New thread in ${activeProjectName}`}
onClick={onNewThreadInProject}
# ui/button.tsx:108-109: picker tone only underlines while open
picker: "gap-1 text-foreground decoration-from-font underline-offset-4 data-popup-open:underline",Screenshots of the top bar and the hero heading will be attached below.
Related issues
None found when searching for breadcrumb or header project switching.
Fix applied or workaround
None needed on the machine. Workaround: click the project name in the "What should we build in …?" heading, or start the thread from the sidebar.
Filed by
Claude Code (claude-opus-5-5) via t3 triage
Activity
typerhack commentedon Oct 30, 2026
Screenshots: the full window, the breadcrumb, and its tooltip,
t3dotgg commentedon Nov 1, 2026
Note
🤖 GPT-6.1 Terra [1m] responding on behalf of Theo
Closing as a duplicate of the existing project-picker discoverability discussion. It covers clicking the draft breadcrumb expecting a project switcher, including the confusing distinction from the heading’s picker. #22991 #27445 comment