Skip to content

[dotnet-port-api] Document Agent Hooks protocol gap - #995

Open
Michelle Clayton (michelle-clayton-work) wants to merge 2 commits into
mainfrom
dotnet-port-api-agent-hooks-gap-20260902-a66b51a6614e2b39
Open

[dotnet-port-api] Document Agent Hooks protocol gap#995
Michelle Clayton (michelle-clayton-work) wants to merge 2 commits into
mainfrom
dotnet-port-api-agent-hooks-gap-20260902-a66b51a6614e2b39

Conversation

@michelle-clayton-work

Copy link
Copy Markdown
Contributor

Summary

Updated docs/dotnet-go-sdk-feature-comparison.md to record the new upstream Microsoft.Agents.AI.AgentHooks public feature as a current Go parity gap. The doc now adds an Agent Hooks matrix row, calls out the missing first-class AGENT-HOOKS protocol package in the runtime misalignment notes, adds the .NET package to the checklist, and raises Agent Hooks support in the prioritized parity opportunities.

This was selected from recent upstream .NET API changes because microsoft/agent-framework#7564 introduced a new public package and options surface (AgentHooksOptions, AsAIAgentWithAgentHooks) while the Go SDK currently exposes only lower-level middleware, history-provider, and context-provider seams.

Ported .NET PRs

None. This is a Go misalignment documentation update prompted by microsoft/agent-framework#7564 and upstream commit 10bf8d7d9ef56304cb6936452e64c90c99850f6c, rather than a runtime/code port.

Breaking Changes

No.

Tests and Examples

  • None added; this is a docs-only comparison update.

Notes

  • Upstream head inspected: microsoft/agent-framework@c3a8aec098c6ef150dbe83ea6626ba27b75e393d.
  • Also checked recent upstream public-surface candidates already covered or in progress in Go nightly work, including concurrent tool invocation, feature-usage telemetry, Responses reasoning include control, and Foundry hosted session/user identity parity.

Generated by .NET to Go API Porting Agent · gpt54 · 352.3 AIC · ⌖ 10.7 AIC · ⊞ 24.4K ·

Closes #975

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟢 Approval recommended

Documentation-only changes appear internally consistent and correctly integrated into the existing comparison structure.

Pull request overview

Updates the .NET vs Go SDK feature comparison document to record the newly introduced upstream .NET Agent Hooks public surface as a current Go parity gap, and to surface that gap consistently across the matrix, misalignment notes, checklist, and prioritized opportunities.

Changes:

  • Updates the contract parity date to reflect the latest comparison pass.
  • Adds “Agent Hooks protocol support” as a first-class matrix row and calls it out in the Agent Runtime misalignment notes.
  • Extends the .NET package checklist and re-prioritizes Go parity opportunities to include Agent Hooks.
File summaries
File Description
docs/dotnet-go-sdk-feature-comparison.md Documents the Agent Hooks parity gap across the comparison summary, feature matrix, misalignment notes, checklist, and priority list.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@github-actions github-actions Bot added kind:docs Changes documentation or comments risk:low Limited blast radius and straightforward rollback labels Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind:docs Changes documentation or comments risk:low Limited blast radius and straightforward rollback size:small At most 30 changed lines across at most 2 files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[dotnet-port-api] Document Agent Hooks protocol gap

2 participants