[BUG] Feature - better detection of iTerm2

Resolved 💬 4 comments Opened Jul 14, 2025 by rubenvarela Closed Dec 10, 2025

Environment

  • Platform (select one):
  • [x] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version: 1.0.51 (Claude Code)
  • Operating System: macos 15.5
  • Terminal: iTerm2 + tmux

Bug Description

When I'm in in tmux on iTerm2, the /terminal-setup command doesn't show. Looks like you're using TERM_PROGRAM which is set to TERM_PROGRAM=tmux. Without tmux, it shows TERM_PROGRAM=iTerm.app.

Steps to Reproduce

  1. tmux
  2. claude code
  3. /terminal-setup

Expected Behavior

The command to work.

Actual Behavior

It's not suggested and doesn't work

Additional Context

Looks like there might be other variables,

Better detection of the terminal in order for the command to work.
Looks like there might be other variables that also mention it.

$ env | grep -i iterm
ITERM_SESSION_ID=w0t0p0:38E31573-FEC0-4D3E-B934-4B853935670A
__CFBundleIdentifier=com.googlecode.iterm2
LC_TERMINAL=iTerm2

Could be interesting as fallback.

View original on GitHub ↗

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