[BUG] /new command selects /init instead of /clear (new) despite being first match

Resolved 💬 3 comments Opened Jan 18, 2026 by flyryan Closed Jan 21, 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 typing /new in the command input, the autocomplete dropdown correctly shows /clear (new) as the first result, indicating "new" is a recognized alias for "clear". However, the selection highlight incorrectly jumps to /init, so pressing Enter executes /init instead of the intended /clear command.

The autocomplete is matching correctly but selecting the wrong item.

What Should Happen?

When typing /new, the /clear (new) option should be both:

  1. Listed first in results (this works correctly)
  2. Selected/highlighted by default, so pressing Enter executes /clear

Error Messages/Logs

N/A - No error messages, just incorrect selection behavior.

Steps to Reproduce

  1. Open Claude Code
  2. Type /new in the command input
  3. Observe the autocomplete dropdown:
  • /clear (new) appears as the first option
  • /init is highlighted/selected instead
  1. Press Enter
  2. /init executes instead of /clear

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.7

Claude Code Version

2.1.12 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

Screenshot attached showing:

  • /new typed in command input
  • /clear (new) listed as first result
  • /init incorrectly highlighted/selected

Workaround: Press Up arrow to manually select /clear (new) before pressing Enter.

Platform note: Using Claude Enterprise (selected "Other" in Platform dropdown)

<img width="1214" height="237" alt="Image" src="https://github.com/user-attachments/assets/64a3f2ce-e9f4-48d1-89e7-bd3fd2dc96f5" />

View original on GitHub ↗

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