Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Project picker is hard to discover: breadcrumb project name looks like a switcher but starts a new thread

Open Beginner friendly
  • Is something wrong?
#27,445 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript
Domain
accessibility, frontend

Research direction

Read apps/web/src/components/chat/ChatHeader.tsx, apps/web/src/components/chat/DraftHeroHeadline.tsx, and the picker tone in apps/web/src/components/ui/button.tsx. Compare the breadcrumb and draft heading interactions, then choose one of the listed affordance changes. Done when a first-time user can recognize how to switch projects and the relevant control behaves as described; the issue does not name a test.

Written by the indexing model from the issue text.

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 to onNewThreadInProject. 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 on main as 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 a ComboboxTrigger rendered as InlineButton tone="picker". In apps/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):

  1. Make the breadcrumb project name open the same project picker, or at least do so when the current thread is an empty draft.
  2. Give the hero project name a resting affordance, such as a chevron, a dotted underline, or a hover background.
  3. 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
  1. Install the desktop app and add at least two projects.
  2. Open a new thread in project A. The top bar shows A / New thread.
  3. Click A in the top bar. Expected: a project list. Actual: no visible change (a new thread in A is "opened" again).
  4. Note that "What should we build in A?" gives no indication that A is 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

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
3h 20m
Merged PRs (30d)
208

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.