TemporalCommunity.Extensions.Agents 0.8.1-preview.18

TemporalAgents

Temporal .NET SDK integrations for building durable AI applications. Two packages, two levels of abstraction:

Both packages give AI workloads durability by default — conversation history, LLM calls, and tool invocations are persisted in Temporal's event history and replayed deterministically after crashes or restarts.

Overview

TemporalCommunity.Extensions.AI

A lightweight middleware layer for Microsoft.Extensions.AI (MEAI). Wraps any IChatClient with Temporal durability via a DelegatingChatClient middleware. No agent framework, no heavy abstractions — just MEAI pipelines made crash-resilient.

Start here if: you are already using MEAI's IChatClient directly and want Temporal durability without adopting the full Agent Framework.

dotnet add package TemporalCommunity.Extensions.AI

Full documentation →

TemporalCommunity.Extensions.Agents

A Temporal integration for Microsoft Agent Framework (Microsoft.Agents.AI). Each AIAgent session maps to a long-lived Temporal workflow with full session management: history, StateBag persistence, HITL approval gates, LLM-powered routing, and parallel agent fan-out.

Start here if: you are building with the Microsoft Agent Framework and want durable, stateful, multi-agent sessions.

dotnet add package TemporalCommunity.Extensions.Agents

Full documentation →

How It Works

Both packages share the same core pattern: LLM calls run inside Temporal activities (never directly in workflows), and conversation turns are delivered via Temporal Updates — a durable, acknowledged request/response primitive that eliminates polling.

External Caller
    │
    │  WorkflowUpdate (chat turn / agent message)
    ▼
Temporal Workflow  ←── persists history, serializes turns, handles ContinueAsNew
    │
    │  ExecuteActivityAsync
    ▼
Activity  ←── calls real IChatClient / AIAgent — retried automatically on failure

Prerequisites

• .NET 10 SDK or later
• A running Temporal server: temporal server start-dev
• An LLM provider (e.g., Azure OpenAI, OpenAI, Ollama)

Samples

Sample credentials

API keys are managed with dotnet user-secrets — stored outside the repo in ~/.microsoft/usersecrets/ and loaded automatically by Host.CreateApplicationBuilder() in the Development environment.

Set OPENAI_API_KEY for each sample project you want to run:

dotnet user-secrets set "OPENAI_API_KEY" "sk-..." --project samples/MEAI/DurableChat

Non-sensitive settings (OPENAI_API_BASE_URL, OPENAI_MODEL, TEMPORAL_ADDRESS) have working defaults in each project's committed appsettings.json and do not need to be set via user-secrets unless you want to override them.

Alternatively, set OPENAI_API_KEY as an environment variable — the samples pick it up automatically via IConfiguration.

# Start Temporal (separate terminal)
temporal server start-dev --namespace default

# Run a sample
dotnet run --project samples/MEAI/DurableChat
dotnet run --project samples/MAF/BasicAgent

Building

just build        # Restore + Release build
just test-unit    # Unit tests (no server required)
just test         # Unit + integration tests (requires temporal server start-dev)
just pack         # Build NuGet packages → artifacts/packages/
just ci           # Full pipeline: clean → build → test-unit → pack

License

MIT