microsoft / microsoft/vscode

Agent host Copilot's built in shell tool does not respect vscode terminal profile

Open
#334,029 0 comments 0 reactions 1 assignee Claimed by @anthonykim1 View on GitHub
agent-host chat-terminal feature-request
Dominant language
TypeScript
Stars
193k
Forks
42.4k
PR merge metrics
PR metrics pending

Description

Moving from local --> agent host Copilot, we've defaulted into going forward with using Copilot SDK's built in shell tool. Meaning `chat.agentHost.customTerminalTool.enabled` false.

What this means is that we went from chat terminal (that agent uses) using pty backed vscode owned terminal to non-interactive and non-pty direct child process spawn to run commands.

Hence the behavior now is that when commands are run from chat agent, it does not respect
`chat.tools.terminal.terminalProfile.windows` or other OS variants.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.