Cmd+N opens new Terminal instead of New Session (desktop app, macOS)

Environment

• Claude Code desktop app, macOS (Darwin 25.5.0)
• Version: 2.1.159
• No custom ~/.claude/keybindings.json (stock bindings)

Description

Pressing ⌘N opens a new integrated Terminal panel rather than creating a new session. Until ~a week ago, ⌘N opened a new session.

The conflict

The File menu still shows ⌘N assigned to "New Session", but pressing ⌘N triggers the Terminal/"New Terminal" action instead. Two menu items appear to both bind ⌘N, and the Terminal action wins, shadowing the documented New Session binding.

Expected vs actual

• Expected: ⌘N creates a new session (matching the File menu).
• Actual: ⌘N opens a new Terminal panel.

Note on keyboard layout (ruled out as cause)

I use a Colemak layout, so I tested whether this was a keycode-vs-character matching issue. It is not — the app matches shortcuts by produced character, consistently:

• Physical "J" key (types n in Colemak) → ⌘N → opens Terminal
• Physical "N" key (types k in Colemak) → ⌘K → opens the command palette ("Open menu ⌘K")

So Colemak is not the cause; this is a genuine in-app ⌘N binding conflict (Terminal vs New Session).

Workaround

The command palette still reaches a new session:

• ⌘K → "New chat" (Enter)
• ⌘3 → New code session
• ⌘2 → New task

Notes

• No local keybinding overrides, so this appears to be a stock binding change/regression introduced in a recent auto-update.