# VS Code Issue #253265 — Agent/Chat Extension Cannot See Terminal Command Output

## Metadata

| Field | Value |
|---|---|
| Institute | Molodetz Institute — Research & Retrieval Division |
| Subject | shell-multiplexer-auto-attach |
| Document type | Source Dossier |
| Tier | 1 |
| Source title | Agent/Chat extension cannot see terminal command output, but shows normally in terminal |
| Source URL | https://github.com/microsoft/vscode/issues/253265 |
| Source publisher / author | Microsoft (vscode repository) |
| Source type | repository |
| Source date (published) | Unknown — not stated |
| Date researched | 2026-10-09 |
| Researched by | tai (agent), model: Claude Sonnet 5, on behalf of retoor |
| Research method | web search synthesis |
| Confidence | Medium |
| Status | Active |

## Summary

A filed VS Code bug where an agent extension's view of a terminal diverges from what a human actually sees rendered in the same terminal — the agent and the human are, in effect, looking at two different realities of the "same" shell session.

## Key findings

- Terminal output visible to a human is not guaranteed to be visible, in the same form, to a program also attached to that terminal — buffering, rendering, and capture paths can diverge.
- This is a second concrete example (alongside #161238) of VS Code's own first-party integration hitting a reliability gap in terminal introspection.

## Pros / strengths

- A specific, filed, reproducible bug report rather than a vague generalization — adds concrete weight to the pattern already established by the other VS Code dossier in this subject.

## Cons / limitations / caveats

- A single bug report; doesn't establish how common or how severe the general class of issue is across tools, just that it occurs in a major one.

## Relevance to tai

Reinforces the same "design for graceful degradation, not perfect detection/capture" principle for the proposal: if a tai control layer captures pane content for its own `grep`/read commands, it should not assume its view will always exactly match whatever VS Code, another tool, or the human sees rendered — and should log/flag divergence rather than silently trusting a possibly-stale capture.

## Changelog

| Date | Change |
|---|---|
| 2026-10-09 | Initial dossier created. |