/terminal-setup error message contradicts itself regarding Windows Terminal support

[philcarbone]

Preflight Checklist

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

What's Wrong?

The /terminal-setup command displays contradictory information about Windows Terminal support.

The error message states: "Terminal setup cannot be run from windows-terminal"

But then immediately instructs: "Run /terminal-setup directly in one of these terminals: Windows: Windows Terminal"

This creates confusion about whether Windows Terminal is actually supported for this feature.

What Should Happen?

The error message should be consistent and provide clear, accurate guidance:

Either:

1. Remove "Windows Terminal" from the supported terminals list if it's not actually supported, OR
2. Fix the detection logic to properly support Windows Terminal

The error message should not contradict itself by both rejecting and recommending the same terminal.

Error Messages/Logs

Steps to Reproduce

1. Open Windows Terminal
2. Run the /terminal-setup command in Claude Code
3. Observe the contradictory error message

Expected vs Actual:

• The error says Windows Terminal is NOT supported: "cannot be run from windows-terminal"
• But then lists Windows Terminal as supported: "Windows: Windows Terminal"

Environment:

• Platform: Windows
• Terminal: Windows Terminal
• This appears to be an error message consistency issue rather than a functional bug

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

Latest (this is an error message consistency issue, not version-specific)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

[philcarbone]

I used CC to submit this with Playwright ;)

[rcocks-hl]

Does anyone know if there is a workaround so we can get shift+enter working in windows terminal?

Update: @IKnewOne provided this workaround downthread: #8208 (comment)

[amchase]

If it helps at all I see this issue in Claude Code 2.0.24 running the most recent versions of both Windows Terminal (1.23.12811.0) and Windows Terminal Preview (1.24.2682.0)

[karstennilsen]

I tried also with an older version Microsoft.WindowsTerminal_1.23.12371.0. Same problem

[Derjyn]

Having this issue with the following environment:

Windows Terminal Preview 1.24.2682.0
PowerShell 7.6.0-preview.5

While this seems like a simple QoL issue, my Shift+Enter muscle memory is ruining chat sessions, or simple mistypes when trying to utilize the \ workaround. Having a fix for this would be a very welcome improvement!

[rcocks-hl]

Having this issue with the following environment:

Windows Terminal Preview 1.24.2682.0
PowerShell 7.6.0-preview.5

While this seems like a simple QoL issue, my Shift+Enter muscle memory is ruining chat sessions, or simple mistypes when trying to utilize the \ workaround. Having a fix for this would be a very welcome improvement!

After spending a week off using claude, I now have the opposite problem, I keep hitting \ + enter, and accidentally sending my co-workers half-finished thoughts on slack!

[zeynalnia]

I'm experiencing this same issue:

• OS: Windows 10.0.26200 (Windows 11)
• Terminal: Windows Terminal (PowerShell 7.5.4)
• Claude Code: Latest version
• Environment variables confirm WT_SESSION is present

[Mecrano]

PowerShell 7.5.4 + Windows Terminal app + Windows 11 also happen