[BUG] tput and width parsing warnings on every command with VSCode extension

Resolved 💬 3 comments Opened Oct 31, 2025 by MCancian Closed Jan 10, 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?

When running commands through Claude Code VSCode extension, every command shows:
tput: No value for $TERM and no -T specified
Error: invalid argument "-" for "-w, --width" flag: strconv.ParseUint: parsing "-": invalid syntax

Environment:

  • OS: Fedora/Bluefin Linux
  • Claude Code: 2.0.25 (VSCode extension)
  • CLAUDE_CODE_ENTRYPOINT: claude-vscode

The warnings appear to come from Claude Code's terminal output processing calling tput/gum
in an environment where TERM is not set, even though TERM is properly set within bash.

What Should Happen?

No warnings

Error Messages/Logs

tput: No value for $TERM and no -T specified
Error: invalid argument "-" for "-w, --width" flag: strconv.ParseUint: parsing "-": invalid syntax

Steps to Reproduce

Any bash commands

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.30

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

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