Bug: Bash tool does not stream live terminal output

Resolved 💬 4 comments Opened Mar 15, 2026 by auto-bias Closed Apr 13, 2026

Bug — VS Code Extension (Claude Code Chat)

When Claude Code runs shell commands via the Bash tool inside the VS Code extension, all output is captured silently and only shown after the command completes. The user sees nothing until the command finishes — which can be many minutes or longer.

This is not a feature request. Live terminal output is essential for:

  • Security & trust: Users must see what commands are doing in real-time on their machine
  • Detecting stuck commands: No way to tell if a command is stuck, hanging, or still running
  • Usability: Any command longer than a few seconds gives zero feedback — builds, tests, installs, deployments
  • Agent reliability: The AI agent itself cannot tell if a command is progressing or stuck, leading to blind retries or timeouts

Not having live output is a fundamental gap. GitHub Copilot and other tools have had this for years — it is a baseline expectation, not a nice-to-have.

Expected behavior

The Bash tool streams stdout/stderr to the user in real-time as the command runs.

Current workaround

User must copy-paste commands and run them manually in their own terminal, which defeats the purpose of an AI coding assistant.

Environment

  • Claude Code VS Code extension
  • Windows 11
  • Long-running commands: Bazel builds, Python pipeline runs

View original on GitHub ↗

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