Skip to content

Add shell exit tool result metadata#314

Merged
anthonykim1 merged 6 commits into
mainfrom
anthonykim1/shellExitMetadata
Jul 8, 2026
Merged

Add shell exit tool result metadata#314
anthonykim1 merged 6 commits into
mainfrom
anthonykim1/shellExitMetadata

Conversation

@anthonykim1

@anthonykim1 anthonykim1 commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Upstream changes from: microsoft/vscode#323922
Also seems like we were behind on npm run generate for changeset related PRs?

@anthonykim1 anthonykim1 self-assigned this Jul 7, 2026
@anthonykim1
anthonykim1 marked this pull request as ready for review July 7, 2026 22:39
@anthonykim1
anthonykim1 requested a review from connor4312 July 7, 2026 22:39
Comment thread types/channels-chat/state.ts Outdated
/** Working directory where the shell command was executed */
cwd?: string;
/** Output preview associated with the shell command, if available */
outputPreview?: string;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we separate this so that terminal output can be streamed?

@anthonykim1 anthonykim1 Jul 7, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if we should take streaming as part of ToolResultShellExitContent in the first place🧐
Maybe under something new like ToolResultShellProgressContent?

I was thinkingToolResultShellExitContent should ideally be for when shell comes back after some kind of exit/completion.

Comment thread types/channels-chat/state.ts Outdated
Comment thread types/channels-chat/state.ts Outdated
Comment thread types/channels-chat/state.ts Outdated
@anthonykim1
anthonykim1 marked this pull request as draft July 7, 2026 22:56
Comment thread types/channels-chat/state.ts Outdated
@anthonykim1
anthonykim1 marked this pull request as ready for review July 8, 2026 02:09
@anthonykim1
anthonykim1 requested a review from roblourens July 8, 2026 02:09
Comment thread types/channels-chat/state.ts Outdated
@anthonykim1
anthonykim1 marked this pull request as draft July 8, 2026 16:22
@anthonykim1
anthonykim1 marked this pull request as ready for review July 8, 2026 17:16
@anthonykim1
anthonykim1 requested a review from connor4312 July 8, 2026 17:16
Comment thread types/channels-chat/state.ts Outdated
Comment thread types/channels-chat/state.ts
@anthonykim1
anthonykim1 merged commit 5dbcb1b into main Jul 8, 2026
9 checks passed
@anthonykim1
anthonykim1 deleted the anthonykim1/shellExitMetadata branch July 8, 2026 17:34
@anthonykim1 anthonykim1 added this to the 1.129.0 milestone Jul 8, 2026
colbylwilliams added a commit that referenced this pull request Jul 8, 2026
Brings in the MCP server start/stop actions (`session/mcpServerStartRequested`
/ `session/mcpServerStopRequested`, #319), the optional `version` field on
`PluginCustomization` (#317), the `ToolResultTerminalCompleteContent` shell
exit tool-result metadata (#314), and the guide/spec docs accuracy pass (#312).

Resolved conflicts:
- The six CHANGELOGs — kept main's new bullets and appended the canvas bullet
  under the current unreleased section (matching main's per-file placement).
- `clients/rust/crates/ahp/src/reducers.rs` — merged the state-import list so it
  keeps both `CanvasState` and main's new `McpServer*State` types (cargo fmt
  re-wrapped).
- `docs/specification/subscriptions.md` — kept main's edits (dropped
  `unsubscribe` from the channel-scoped command row; reworded the
  resource-watch id as "receiver-assigned") and re-added the canvas rows.

Regenerated all client artifacts and schemas; the canvas channel still
registers its actions at spec 0.5.2 and PROTOCOL_VERSION is unchanged.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants