[DOCS] /terminal-setup message is misleading for unsupported terminals like gnome-terminal

Resolved 💬 4 comments Opened Dec 19, 2025 by criptocoko Closed Feb 28, 2026

Documentation Type

Unclear/confusing documentation

Documentation Location

claude code /terminal-setup on gnome-terminal

Section/Topic

doc /terminal-setup

Current Documentation

When running /terminal-setup from gnome-terminal, the message says:

Terminal setup cannot be run from gnome-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:

• IDE: VSCode, Cursor, Windsurf
• Other: Ghostty, WezTerm

  1. Return to tmux/screen - settings will persist

What's Wrong or Missing?

The message wording is ambiguous. I interpreted it as "the command cannot execute here, go run it elsewhere and come back." So I ran it in VSCode terminal (following the steps on the message), came back to gnome-terminal, and expected Shift+Enter to work - but it doesn't.

The actual meaning is that gnome-terminal doesn't support this feature at all.

Suggested Improvement

  1. Change the wording to something like:
  • "The Shift+Enter shortcut is not supported in gnome-terminal."
  • "This feature cannot be configured for gnome-terminal."
  1. Clarify that the steps below are for users who want to switch to using Claude Code in those terminals, not for configuring something that will work when returning to the current terminal:

If you'd like to use this shortcut, run Claude Code from one of these supported terminals instead:
• IDE: VSCode, Cursor, Windsurf
• Other: Ghostty, WezTerm

Impact

High - Prevents users from using a feature

Additional Context

_No response_

View original on GitHub ↗

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