Community contribution: Squad.Agents.AI - .NET adapter for Microsoft Agent Framework #1205

What

Squad.Agents.AI is a .NET library that wraps the Squad CLI as a Microsoft.Agents.AI.AIAgent, so .NET apps using the Microsoft Agent Framework (MAF) can use Squad agents alongside other AI participants — workflows, Semantic Kernel chains, or other MAF agents — without shelling out or reimplementing the CLI protocol.

I'd like to contribute this as a community package. The work is done and I'm looking for your signal on whether you'd accept it upstream.

Why this matters

In #1144 I described the gap: when Squad is embedded in a host process (no REPL), the integration surface is manual. This adapter closes that gap for .NET consumers. It handles CLI lifecycle, streaming, session management, and keyed DI registration so the host just calls agent.RunAsync(activity, turnState) and gets structured responses.

What's in the PR

• Squad.Agents.AI NuGet package targeting .NET 8 and .NET 9
• 43 tests, CI green on both ubuntu and windows
• DI registration shapes: default services.AddSquadAgent(opts => ...), named via services.AddSquadAgent("agent-name", opts => ...) (binds to ConnectionStrings:squad-{name}), and Microsoft.Extensions.DependencyInjection keyed services via services.AddKeyedSquadAgent("key", opts => ...)
• BYOK support via ConfigureCopilotClient delegate
• Streaming via IAsyncEnumerable<StreamingActivity>
• Sample app + README with quickstart

What's NOT included (deferred)

• Aspire-orchestrated sample (depends on Squad telemetry contract from Squad telemetry from embedded host processes (Agent Framework wrappers, no REPL): how should it reach Aspire? #1144)
• SDK ToString() redaction (requires upstream Copilot SDK change)
• Multi-agent orchestration patterns (v0.2 scope)

The question

Are you open to accepting this as a community contribution? If yes, I'll open a cross-fork PR targeting dev with Closes #N per CONTRIBUTING.md.

On placement: I want to flag that this is a .NET package in a JS-first monorepo. Two paths I see:

1. In-repo under src/Squad.Agents.AI/ — discoverable, single repo for all Squad code. The .NET CI workflow is isolated and only triggers on that path.
2. Companion repo (e.g. Squad.Agents.AI) — keeps the npm monorepo clean, lets the .NET package version independently.

I'm fine with either. If you have a preference or a third option, happy to adapt.

Related

• Squad telemetry from embedded host processes (Agent Framework wrappers, no REPL): how should it reach Aspire? #1144 — Squad telemetry from embedded host processes (the scenario this adapter enables)