Audit deprecated Copilot SDK terminal content usage

Open
#323,947 0 comments 0 reactions 1 assignee View on GitHub

@anthonykim1 is already working on this.

Since Jul 1, 2026.

Assessment

This issue has not been assessed yet.

Description

Follow-up from https://github.com/microsoft/vscode/pull/323922 and https://github.com/github/copilot-sdk/issues/1803.

Copilot SDK now exposes shell_exit for shell command exit metadata, and SDK terminal content is deprecated for that purpose. I want to make sure we do not keep depending on SDK type: "terminal" content for new shell status behavior.

From a quick audit, the Agent Host ToolResultContentType.Terminal usages are not the same thing as the deprecated SDK terminal content. Those are VS Code/AHP terminal resource references with a terminal URI, and should stay separate from SDK shell_exit metadata.

Actual deprecated SDK terminal-content dependency found:

Places checked that are probably not deprecation debt:

Work:

  • Confirm whether the internal Copilot CLI extension path should keep supporting SDK terminal content for glob/grep/rg result parsing as legacy compatibility.
  • If not, migrate search result parsing to result.content or another non-deprecated SDK content shape.
  • Keep shell_exit limited to shell command exit metadata; do not treat it as display output or as a live terminal resource.
  • Rename or update tests so any remaining SDK terminal coverage is clearly marked as legacy compatibility.
  • Make sure Agent Host ToolResultContentType.Terminal remains documented as a VS Code/AHP terminal resource, not deprecated SDK terminal content.

This is mostly cleanup/debt after adopting shell_exit; I do not think it blocks the command decoration fix.

Dominant language
TypeScript
Stars
193k
Forks
42.9k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode

All issues in microsoft/vscode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.