Repository navigation
Conversation
Add docs/develop/python/integrations/agent-framework.mdx for the temporalio-agent-framework plugin, register it first in the Python Integrations sidebar category, list it on the Python SDK index page, and add its IntegrationsGrid entry. The snippet blocks are empty on purpose. They reference markers in the samples-python agent_framework_plugin samples, which are not on main yet. Run yarn snipsync after that PR merges, before marking the docs PR ready.
Describe the streamed Activity result as the plugin now records it: text runs and tool-call argument deltas merged, one payload under the 2 MiB limit, and a retried stream publishing from its first update again. State the Python floor as the plugin's requires-python, lead the install with the package alone and move the mcp extra to the MCP section, match the middleware and approval prose to the samples (a Decision with the request id, a validator that checks the input, a handler that checks the state), explain add_temporal_spans=True and show the tracer provider call, give the heartbeat numbers, and spell out identifier outside code.
Say that each published streaming batch is a Signal that counts toward the 10,000 a Workflow Execution can receive, so a chat that streams has to Continue-As-New sooner, and name that limit as the second non-retryable StreamError case. Make the unknown-model-name failure per Worker, add the MCP tool classes and the OpenTelemetry globals to the limitations list, describe the lock, end_chat Signal and transcript Query the continue-as-new snippet shows, and apply the wording nits: run commands for hello world, exhausted MCP Activities, run-level tool collisions, the MCPPlugin name clash, compaction, the OTLP endpoint variable, and "Out of scope" as the label.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Snipsync coverageSDK code lines in
All sectionsAll languages: 50.1% (24,523 of 48,936 lines).
Compared with |
Contributor
📖 Docs PR preview links
|
The short name is too generic: any vendor, Temporal included, could publish an agent framework, so the integration takes the product's full name. The plugin and the samples are renamed the same way, and the page's slug, sidebar entry, grid href, install commands, imports, class, error and Activity names and links follow them.
The plugin changed after the second review: a client with streaming_topic now runs every call through the streaming Activity and publishes on each one, batches cap at 256 updates, activity_as_tool needs a timeout when the tool is built, a raising or wrong-type factory fails the Activity once with a typed error, hosted MCP headers move to the Worker through hosted_mcp_headers, sync tools run inline through a rebound asyncio.to_thread, and Retry-After dates are parsed. Say each of those, and add the loop settings, the unanswered-approval behavior, the version-qualified MCP heartbeat sentence and the unregistered-server case.
DABH
added a commit
to temporalio/ai-integrations
that referenced
this pull request
Nov 13, 2026
The release-stage link pointed at a docs page that is not merged yet (temporalio/documentation#5712). python/mcp uses the plain label for the same reason.
The plugin changed after a maintainer review: the plugin goes on Client.connect, because only a plugin on the Client sets the data converter and provider imports must stay out of the sandboxed Workflow file; TemporalChatClient sends store=False unless set; a factory that raises is retried while None or a wrong type fails once; the stream error type is MicrosoftAgentFrameworkStreamError; MCP tool names are normalized as MCPTool does and temporalio-mcp is described at 0.3 only; client_kwargs are recorded in Event History and credential headers are refused; structured output sends the strict schema; prompts arriving mid-run must be carried across Continue-As-New; Retry-After parses as seconds or milliseconds, capped at 60 seconds; the seam error names the tested range.
The plugin now requires temporalio-mcp 0.4, whose MCP Activities heartbeat by default with a 10-second heartbeat timeout, so a cancel reaches a running request and a lost Worker is noticed within seconds. Replace the sentence that said the provider sets no heartbeat timeout and that 0.3 does not heartbeat, name the heartbeat_timeout option on TemporalMCPToolProvider (None turns heartbeats off), and name the 0.4 floor where the mcp extra is installed.
The plugin now defines its tested range as the floor it was first tested on through the version its lock pins, which CI runs on every change, so the range is 1.23.0 through 1.24.0; the runtime seam error names that range. For a hosted MCP connector tool, the authorization entry in hosted_mcp_headers goes to the tool's authorization field as the bare token, with a leading "Bearer " dropped, because the Responses API takes the bare token there.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds
docs/develop/python/integrations/microsoft-agent-framework.mdx, the guide for the Temporal Python plugin for Microsoft Agent Framework, with the sidebar entry, the Python index bullet and the integrations grid card. The page covers install, hello world, Activity-backed tools, MCP, middleware, approvals, structured output, streaming, Continue-As-New and OpenTelemetry, and ends with the plugin's limits.Notes to reviewers
The plugin is merged (temporalio/ai-integrations#522). Its first pre-release (0.0.1rc1) is on TestPyPI only, so the page names the package as it will be on PyPI and claims no version. The 17 code blocks are snipsync markers from temporalio/samples-python#418 and stay empty until that PR merges after the PyPI release;
yarn snipsyncthen fills them, staging only this file, and the PR can be marked ready. The page stays a draft until then. The branch is merged with main; Vale with the CI config, the snipsync-marker check and the orphan check pass.