[BUG] Marketplaces > Browse Plugins: Enter for details navigates to Discover tab instead

Resolved 💬 2 comments Opened Jan 20, 2026 by jmcdonald Closed Jan 20, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When browsing plugins from a custom marketplace, pressing Enter to view plugin details incorrectly navigates back to the main Discover tab instead of showing the plugin details within the Marketplaces context.

Additionally, the top navigation state incorrectly reverts to show Discover as the active tab when the user should still be in the Marketplaces flow.

What Should Happen?

  1. Pressing Enter on a highlighted plugin should display plugin details while remaining in the Marketplaces context
  2. The top navigation should continue to show Marketplaces as the active tab throughout this flow

Error Messages/Logs

No error messages. Navigation silently redirects to wrong location.

Steps to Reproduce

  1. Run claude in terminal
  2. Type /plugin
  3. Tab to Marketplaces
  4. Select a marketplace that has plugins available
  5. Select Browse Plugins
  6. Highlight a plugin using arrow keys
  7. Press Enter to view details
  8. Expected: Plugin details shown, still in Marketplaces context, top nav shows Marketplaces
  9. Actual: Navigates to Discover tab, top nav shows Discover as active

Claude Model

Opus 4.5

Is this a regression?

Unknown

Last Working Version

N/A

Claude Code Version

2.1.12

Platform

Claude Max

Operating System

macOS (Darwin 25.2.0)

Terminal/Shell

Ghostty / zsh

Additional Information

Related issues:

  • #19382 — Spacebar toggle also broken in this same Marketplaces browse flow

This appears to be part of a broader issue with the Marketplaces browse UI having incorrect navigation targets and incomplete keyboard event handling. The Marketplaces browse view seems to be routing actions to the Discover view instead of handling them internally.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗