terminal-setup command should support standard Linux terminals (gnome-terminal, xterm, etc.)

Resolved 💬 3 comments Opened Oct 21, 2025 by pele1410 Closed Jan 8, 2026

Problem

The /terminal-setup command fails to work in standard Linux terminal emulators, only supporting a small subset of modern IDE-integrated terminals and a couple of newer standalone terminals.

When running /terminal-setup in gnome-terminal, the command refuses to run with:

Terminal setup cannot be run from gnome-terminal.

Affected Terminals

This limitation excludes ubiquitous Linux terminals including:

  • gnome-terminal (one of the most common Linux terminals)
  • xterm
  • konsole
  • xfce4-terminal
  • GNOME Console
  • Most standard terminal emulators on Linux

The command only works in:

  • VSCode, Cursor, Windsurf (IDE terminals)
  • Ghostty, WezTerm (newer terminals)

Why This Matters

Linux users working in standard terminal environments are excluded from this feature. This particularly affects:

  • Server administrators
  • Developers using traditional terminal setups
  • Users running tmux/screen in standard terminals
  • Anyone using the default terminal on major Linux distributions

Expected Behavior

The terminal-setup command should either:

  1. Support standard terminals via ANSI escape sequences/terminfo
  2. Provide manual setup instructions for unsupported terminals
  3. Clearly document this limitation upfront in the documentation
  4. Be removed if broad terminal support cannot be achieved

Environment

  • Terminal: gnome-terminal
  • Platform: Linux (Fedora 41)
  • Claude Code: latest version

Impact

A CLI tool designed for developers should work in standard developer terminals. This limitation excludes a significant portion of the Linux user base from accessing what appears to be a core feature.

View original on GitHub ↗

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