{"version":"2.1.301","anchor":"linux-vte-terminal-detection-reworked","canonical_anchor":"linux-vte-terminal-detection-reworked","heading":"Linux detection of VTE-based terminals works differently","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/linux-vte-terminal-detection-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Linux detection of VTE-based terminals works differently\n\nOn Linux, Claude Code now uses a dedicated check to spot VTE-based terminals such as GNOME Terminal instead of a list of other terminals' variables\n\n**What**\n\nVTE is the terminal library behind GNOME Terminal and several other Linux terminals. Claude Code now decides whether you are in a VTE-based terminal with a dedicated check that recognises those terminals and excludes terminal multiplexers (programs like tmux that run several terminals inside one) and other terminal programs.\n\nBefore, it ruled terminals out by looking at environment variables set by xterm, Alacritty, Kitty and WezTerm. When the check matches, Claude Code picks a setting labelled `none(vte)`.\n\n**Why**\n\nOn Linux this may change how Claude Code handles terminal output, depending on which terminal you use.\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}