[BUG] /terminal-setup command

Resolved 💬 3 comments Opened Jan 14, 2026 by FlorentCoulonBS Closed Feb 27, 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 I launch this command on Windows terminal, it doesn't switch to shift + Entrée and remain on ctrl with this strange message. Please advice :

/terminal-setup
⎿ Terminal setup cannot be run from windows-terminal.

This command configures a convenient Shift+Enter shortcut for multi-line prompts.
Note: You can already use backslash ( + return to add newlines.

To set up the shortcut (optional):

  1. Exit tmux/screen temporarily
  2. Run /terminal-setup directly in one of these terminals:

• Windows: Windows Terminal
• IDE: VSCode, Cursor, Windsurf, Zed
• Other: Alacritty, Warp

  1. Return to tmux/screen - settings will persist

Note: iTerm2, WezTerm, Ghostty, and Kitty support Shift+Enter natively.

What Should Happen?

when you launch this command, the keyboard should switch to shift + Enter instead of ctrl + Enter

Error Messages/Logs

⎿  Terminal setup cannot be run from windows-terminal.

     This command configures a convenient Shift+Enter shortcut for multi-line prompts.
     Note: You can already use backslash ( + return to add newlines.

     To set up the shortcut (optional):
     1. Exit tmux/screen temporarily
     2. Run /terminal-setup directly in one of these terminals:
     • Windows: Windows Terminal
     • IDE: VSCode, Cursor, Windsurf, Zed
     • Other: Alacritty, Warp
     3. Return to tmux/screen - settings will persist

Steps to Reproduce

Launch /terminal-setup

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.7 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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