Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Python: [Feature]: Official first-class TypeScript SDK support

Aperta
  • Qualcosa non va?
#9,226 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@rogerbarreto ci sta già lavorando.

Dal 8/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

.NET agents python
Problem

Microsoft Agent Framework currently provides official SDKs for .NET and Python, but not TypeScript. For applications whose frontend, backend, shared domain models, tooling, and deployment are primarily TypeScript, adopting Agent Framework requires introducing and operating a separate .NET or Python service.

That adds another runtime, dependency ecosystem, build pipeline, deployment unit, security-patching process, and set of duplicated contracts. It also makes it harder to share validated types and business logic between the existing application and its agents.

This is related to #1216, but this request is specifically for an official, first-class TypeScript implementation: authored and maintained as TypeScript, distributed through npm with native typed APIs, and treated as a supported Agent Framework SDK rather than only a generic JavaScript runtime package or protocol client.

Use Case and Evidence

We are evaluating Agent Framework for an application that is predominantly TypeScript. The application already uses TypeScript across its UI and server components, and its developers, domain models, validation schemas, tests, and operational tooling are centered on the Node.js ecosystem.

To use Agent Framework today, we would need to:

  • Build a separate Python or .NET agent service.
  • Recreate or generate contracts between TypeScript and the agent service.
  • Operate an additional runtime and deployment lifecycle.
  • Duplicate authentication, authorization, telemetry, error handling, and configuration integration.
  • Split debugging and local development across language boundaries.

These costs can determine whether a team adopts Agent Framework or chooses a TypeScript-native alternative, even when Agent Framework otherwise provides the preferred capabilities.

Desired Outcome

Provide an officially supported TypeScript SDK that allows Node.js and TypeScript applications to build Agent Framework agents and workflows without introducing a Python or .NET service.

A successful outcome would provide idiomatic, strongly typed TypeScript APIs for the core framework capabilities, with clear compatibility and feature-parity documentation relative to the .NET and Python SDKs. A phased implementation would be valuable even if complete parity cannot be delivered initially.

Alternatives Considered
  • Python or .NET sidecar service: Technically workable, but adds operational complexity and prevents direct reuse of TypeScript domain code and types.
  • AG-UI, A2A, or custom HTTP integration: Useful for connecting a TypeScript client to a remote agent, but does not let TypeScript developers author Agent Framework agents and workflows natively.
  • Direct model-provider SDKs: Support model calls and tool calling, but do not provide the same Agent Framework abstractions and cross-language consistency.
  • Other TypeScript-native agent frameworks: Avoid the additional runtime but mean giving up Agent Framework compatibility and Microsoft's unified framework direction.
Proposed Direction

Consider an official npm package, such as @microsoft/agent-framework, initially covering a focused set of core capabilities:

  • Agents, messages, tools, structured output, and streaming
  • Workflow composition and agent handoffs
  • Session and conversation-state abstractions
  • Middleware and observability hooks
  • MCP, A2A, and AG-UI interoperability
  • Microsoft Foundry and common model-provider integrations

Publishing a support matrix and roadmap would help teams adopt an initial release while understanding differences from the .NET and Python implementations.

Scope and Non-Goals
  • This request does not require immediate one-to-one parity with every .NET and Python integration.
  • A modern Node.js/TypeScript baseline and phased delivery would be reasonable.
  • This is not only a request for generated type declarations over an unrelated JavaScript client; the goal is an officially maintained TypeScript Agent Framework SDK with idiomatic APIs and a documented compatibility commitment.
Language

Other / Not Applicable

Contribution Intent

I am willing to implement this

Acknowledgements
  • I searched existing issues and did not find a duplicate.
  • I will wait for explicit maintainer agreement before starting implementation of a non-trivial change.
Lingua principale
Python
Stelle
14k
Fork
2.5k
Merge medio
2g 10h
PR unite (30g)
424

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/agent-framework

Tutte le issue di microsoft/agent-framework

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.