[dotnet-port-api] Document MCP Tasks extension gap

[github-actions]

Summary

Updated docs/dotnet-go-sdk-feature-comparison.md after reviewing the upstream .NET MCP Tasks extension work in microsoft/agent-framework#7774 and commit 96560bbf65973d098e09f38cc69f45826845d08e. The comparison now explicitly records that .NET MCP client tools support task-aware wrappers with polling, input requests, and best-effort remote cancellation, while Go still exposes only the basic mcptool.Connect/ListTools bridge.

I selected a docs realignment rather than a code port because the complete upstream change would require new public Go MCP APIs and lower-level task-extension support that is not yet present in the current Go MCP stack.

Ported .NET PRs

• microsoft/agent-framework#7774 - Migrate MCP long-running task support to the 2026-07-28 Tasks extension; this PR documents the resulting Go parity gap instead of attempting an oversized code port.

Breaking Changes

No.

Tests and Examples

• No code changes; no tests or examples were added or updated.

Notes

• Checked for existing Go tracking work referencing #7774, 2026-07-28 Tasks extension, or ListAgentToolsWithTasks; none was found.
• The current Go MCP bridge depends on github.com/modelcontextprotocol/go-sdk/mcp and currently exposes basic tool listing/invocation plus input_required result handling, but not task-aware wrapper APIs analogous to .NET McpTaskOptions / ListAgentToolsWithTasksAsync.

Generated by .NET to Go API Porting Agent · gpt54 · 304.1 AIC · ⌖ 11.6 AIC · ⊞ 24.4K · ◷

---

Note

This was originally intended as a pull request, but GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch dotnet-port-api-mcp-tasks-gap-doc-5fb0599bd2d18f28.

Click here to create the pull request

To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ

Show patch preview (45 of 45 lines)

From 799fe2a7cbb2c50a25c8a9b89a5f62cd586454d9 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Fri, 28 Aug 2026 08:14:27 +0000
Subject: [PATCH] [dotnet-port-api] Document MCP Tasks extension gap

Update the .NET/Go feature comparison to call out the new .NET MCP Tasks extension surface and the corresponding Go gap in task-aware MCP client tooling.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 docs/dotnet-go-sdk-feature-comparison.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/dotnet-go-sdk-feature-comparison.md b/docs/dotnet-go-sdk-feature-comparison.md
index 5f932933b..b9dedc59e 100644
--- a/docs/dotnet-go-sdk-feature-comparison.md
+++ b/docs/dotnet-go-sdk-feature-comparison.md
@@ -1,6 +1,6 @@
 # .NET and Go SDK Feature Comparison
 
-Date: July 2, 2026
+Date: August 28, 2026
 
 This document compares the .NET SDK at `microsoft/agent-framework/dotnet` with the Go SDK in this repository. It is based on the package, sample, and public API inventory present on this date.
 
@@ -43,7 +43,7 @@ Within overlapping features, the main misalignments are API shape and ecosystem
 | Hosted/server-side tools | Foundry/OpenAI samples for code interpreter, file search, web search, OpenAPI, Bing custom search, SharePoint, Microsoft Fabric, memory search, Toolbox, hosted MCP. | `tool/hostedtool` declarations for web search, file search, code interpreter, MCP server; Foundry-first samples cover code interpreter, web search, MCP client tools, and local MCP tools; OpenAI Responses hosted-tool coverage remains provider-specific. | Partial | Go has declaration types and initial Foundry/OpenAI Responses hosted-tool coverage, but fewer service-specific Foundry hosted tool integrations and no Foundry toolbox lifecycle sample. |
 | Agent as function tool | Agents can be converted/bound as tools in samples and workflow builders. | `tool/agenttool.New` wraps an agent as a `Func
... (truncated)