Skip to content

protocol: add InitializeResult extension metadata - #420

Merged
roblourens merged 1 commit into
mainfrom
agents/add-meta-to-initialize-result-contract
Aug 26, 2026
Merged

protocol: add InitializeResult extension metadata#420
roblourens merged 1 commit into
mainfrom
agents/add-meta-to-initialize-result-contract

Conversation

@roblourens

Copy link
Copy Markdown
Member

Summary

  • add optional InitializeResult._meta for namespaced, implementation-specific extension capabilities
  • document unknown-key handling and when capabilities should graduate to typed protocol fields
  • regenerate schemas and all client mirrors
  • add a shared conformance fixture proving nested metadata round-trips across clients

This supports the VS Code-owned chat-targeted state-file capability needed by microsoft/vscode#332820.

Validation

  • npm run generate
  • npm run test (440 passed; 100% reducer coverage)
  • TypeScript round-trip corpus (3 passed)
  • Go round-trip corpus
  • Rust round-trip corpus (1 passed)
  • Swift round-trip corpus (1 passed)
  • Kotlin round-trip corpus (all 44 fixtures passed)
  • .NET test project (535 passed)

(Written by Copilot)

Allow hosts to advertise namespaced implementation-specific capabilities in initialize responses and preserve them across generated clients. (Written by Copilot)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@roblourens
roblourens merged commit a0bc67f into main Aug 26, 2026
9 checks passed
@roblourens
roblourens deleted the agents/add-meta-to-initialize-result-contract branch August 26, 2026 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants