aaif-goose/goose

[BUG] Cmd+T / Ctrl+T keyboard shortcut for new chat is not working

Open

#9,523 opened on May 30, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (45,211 stars) (4,628 forks)batch import
good first issue

Description

Describe the bug The keyboard shortcut Cmd+T (macOS) / Ctrl+T (Windows/Linux) for starting a new chat in Goose Desktop is not working. Users have to manually click the "New Chat" button every time they want to start a new session.

To Reproduce Steps to reproduce the behavior:

  1. Open Goose Desktop
  2. Start a conversation
  3. Press Cmd+T (macOS) or Ctrl+T (Windows/Linux)
  4. Nothing happens — the app does not navigate to the Home screen to start a new chat

Expected behavior Pressing Cmd+T / Ctrl+T should take the user to the Home tab, allowing them to start a new chat session (same behavior as clicking the "New Chat" button).

Environment

  • Goose Desktop (all platforms affected)
  • Previously implemented in PR #4541 / Issue #4535

Additional context

  • This feature was previously added via PR #4541 ("Added CMD+T keyboard shortcut that takes you to the Home tab")
  • The original feature request was Issue #4535
  • The shortcut appears to have regressed / stopped working in recent builds
  • The only workaround is to manually click the "New Chat" button

Contributor guide

Tech stack
rusttypescript
Domain
desktopfrontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitRustTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Inspect the keyboard shortcut implementation, likely in the UI layer (e.g., Tauri or Electron). Compare with the previous implementation in PR #4541 to identify what changed.