claude-code - 💡(How to fix) Fix VSCode Extension: Interactive terminal integration (write to and read from VSCode terminal)

Feature Request

GitHub Copilot has the ability to interact directly with the VSCode integrated terminal — commands are injected into the active terminal, and both input and output are visible to the user in real time.

Claude Code's current behavior: The Bash tool runs commands in a background subprocess. The user cannot see the commands being typed or the output in their VSCode terminal. This requires the user to be present at the PC to copy-paste every command manually when they want to follow along or verify what is happening.

Desired Behavior

Claude Code should be able to:

1. Write commands directly into an open VSCode terminal
2. Show both input (the command) and output (the result) in the VSCode terminal, visible to the user in real time
3. Allow the user to optionally approve each command before execution (for safety)

Use Case / Motivation

When Claude is helping with server administration, debugging, or any multi-step terminal workflow, the user currently has to:

• Copy each command from Claude's response
• Paste it into a terminal manually
• Copy the output back if Claude needs to see it

With proper terminal integration, Claude could run the commands directly and the user could watch in real time — much more natural and efficient collaboration.

Impact

This is a significant UX gap compared to GitHub Copilot's terminal integration. It makes Claude Code feel less capable for terminal-heavy workflows even though it can already execute commands via the Bash tool.

Environment

• Claude Code VSCode Extension
• Platform: macOS (darwin)

🤖 Created with Claude Code