[BUG] /terminal-setup fails on Windows Terminal despite listing it as supported
Resolved 💬 2 comments Opened Apr 10, 2026 by malbolgeunshackled Closed May 6, 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?
Running /terminal-setup inside Claude Code on Windows Terminal gives the error:
Terminal setup cannot be run from windows-terminal.
However, the same output then lists Windows Terminal as a supported terminal:
This is contradictory — it detects the terminal as "windows-terminal," refuses to run, but then tells me to run it in Windows Terminal.
What Should Happen?
The Shift+Enter shortcut should be configured for Windows Terminal.
Error Messages/Logs
The command fails with "Terminal setup cannot be run from windows-terminal."
Steps to Reproduce
- Open Windows Terminal on Windows 11
- Launch Claude Code (claude)
- Run /terminal-setup at the Claude Code prompt
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.100
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗