6e95517659
* Python: Split type checkers by target (pyright source, 5 checkers on tests/samples) Rework the typing setup along the lines of the 'too many type checkers' approach: - Pyright (strict) is now the sole source-code type checker; mypy is removed from source and its [tool.mypy] block becomes a relaxed profile used only for tests/samples. - Tests are checked by all five checkers (pyright relaxed, mypy, pyrefly, ty, zuban); samples by pyright, pyrefly, and ty. All run in a relaxed/ basic profile so authors aren't forced into over-annotation. - Add pyrightconfig.tests.json and bump sample pyright configs to basic. - Unify test/sample typing onto the same parallel fan-out used by source pyright via run_command_items in task_runner.py. - Make version-conditional imports symmetric: keep or drop the '# type: ignore' on both branches so results match across interpreter versions (local vs CI). - Update SKILL.md, DEV_SETUP.md, and CODING_STANDARD.md for the five gating checkers and pyright on source+tests+samples. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Python: Fix merge regressions from main (typing + runtime) Merging main into the type-checker split branch surfaced regressions that the new five-checker test suite and unit tests caught: Runtime fixes: - anthropic: restore the dropped `cache_read_input_token_count` mapping in _parse_usage_from_anthropic (lost during merge conflict resolution). - gemini: _get_function_calling_mode test helper returned str(enum) ('FunctionCallingConfigMode.AUTO') instead of the enum value ('AUTO'). - openai: _response_id_from_token test helper was an infinite self-recursion; return token['response_id']. - orchestrations: reset output_events per approval iteration so the terminal output assertion counts only the final run. - core: drop a stale duplicate harness test whose message ('non-negative') contradicted the source ('positive'). - purview: import PolicyLocation/PolicyScope/ProtectionScopeActivities/ ExecutionMode used by the processor tests. Type-checker fixes (tests, relaxed profile): - core: pyright/mypy/pyrefly/ty/zuban green-ups across the harness, MCP, observability and types tests. - anthropic/openai: route provider-namespaced UsageDetails keys through a dict cast (extra_items TypedDict unsupported by mypy/ty). - purview: typed model constructors and cache-mock casts. - ag-ui: annotate WorkflowContext[Any, Any] so yield_output accepts test payloads, guard Optional forwarded_props, and ty-ignore intentional bad args. Source pyright (sole source checker) flagged unnecessary ignores newly introduced by merged code in core _tools.py and declarative _declarative_base.py. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Python: Isolate per-package mypy cache in test-typing fan-out The parallel test-typing fan-out runs many mypy processes concurrently, all defaulting to a single shared ./.mypy_cache. Concurrent writes corrupt the cache and mypy aborts with INTERNAL ERROR (intermittently, depending on worker timing) -- which is why CI's Test Typing job failed on a shifting set of packages while a single-package run was fine. Give each mypy invocation an isolated cache dir keyed by its target paths so incremental caching still works per package without races. Other checkers (zuban/pyrefly/ty/pyright) maintain their own caches and are unaffected. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Python: Make lab pyright-only on source (drop source mypy) Lab was the last package still running mypy on its source code, requiring mypy-only `# type: ignore` comments that pyright (the sole source checker everywhere else) flags as unnecessary. Align lab with the rest of the monorepo: - Remove the lab source mypy poe tasks (mypy-gaia/lightning/tau2) and the now-dead strict [tool.mypy] config block. - Drop the 'Run lab mypy' CI step; lab source is type-checked by pyright only. Lab tests remain covered by the workspace test-typing fan-out (mypy, pyrefly, ty, zuban, pyright over tests using the relaxed root config). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Python: Fix test-typing regressions from latest main merge A fresh merge from main brought in new test code never run under the five-checker test-typing suite. Green up across the affected packages: - core: narrow Optional span.attributes with 'and' guards in span filters and assert+cast the json.loads(...attributes[...]) reads (test_observability); match the existing as_agent ignore on the protocol-typed fixture (test_clients). - openai: align new streaming tests with the established chat_options dict pattern (ChatOptions TypedDict isn't assignable to dict), route Optional .annotations[0] access through a small _first_annotation helper (mirrors the file's assert-not-None convention), and annotate a mapped ResponseStream. - foundry_hosting: annotate error: dict[str, Any] = body.get(...) or {} (zuban needs the annotation). - foundry: narrow ignores for the live AIProjectClient credential arg (pyrefly) and connections.get_default (zuban) SDK type gaps. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * updated pyright version * pyright fix * Python: Fix source typing for pyright 1.1.410 Pyright 1.1.410 tightened several checks. Apply the same source fixes as upstream PR #6275: - anthropic: import AsyncAnthropicBedrock from anthropic.lib.bedrock and AsyncAnthropicVertex from anthropic.lib.vertex (no longer re-exported from the anthropic top-level package -> reportPrivateImportUsage). - core _types.py: cast the transform-hook result to UpdateT (reportAssignmentType). - core _workflows/_events.py: annotate the @contextmanager helper as Generator[None] instead of Iterator[None] (reportDeprecated). - redis: build the combined filter expression with an explicit loop instead of reduce(and_, ...), which pyright could no longer fully type (drops the now unused functools.reduce / operator.and_ imports). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Python: Accept plain-text body in Azure Functions workflow/run endpoint The workflow_orchestrator already accepts plain strings as well as JSON objects via context.get_input(), but the start_workflow_orchestration HTTP handler only accepted JSON and returned 400 for any non-JSON body. This made the functions integration tests that POST text/plain to /api/workflow/run (e.g. test_09_workflow_shared_state) fail consistently with 400 != 202. Fall back to the raw request body (decoded as UTF-8) when the body is not JSON, rejecting only a truly empty body. The JSON path is unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
221 lines
8.7 KiB
Python
221 lines
8.7 KiB
Python
# Copyright (c) Microsoft. All rights reserved.
|
|
|
|
"""
|
|
DeepResearch workflow sample.
|
|
|
|
This workflow coordinates multiple agents to address complex user requests
|
|
according to the "Magentic" orchestration pattern introduced by AutoGen.
|
|
|
|
The following agents are responsible for overseeing and coordinating the workflow:
|
|
- ResearchAgent: Analyze the current task and correlate relevant facts
|
|
- PlannerAgent: Analyze the current task and devise an overall plan
|
|
- ManagerAgent: Evaluates status and delegates tasks to other agents
|
|
- SummaryAgent: Synthesizes the final response
|
|
|
|
The following agents have capabilities that are utilized to address the input task:
|
|
- KnowledgeAgent: Performs generic web searches
|
|
- CoderAgent: Able to write and execute code
|
|
- WeatherAgent: Provides weather information
|
|
|
|
Usage:
|
|
python main.py
|
|
"""
|
|
|
|
import asyncio
|
|
import os
|
|
from pathlib import Path
|
|
from typing import Any
|
|
|
|
from agent_framework import Agent
|
|
from agent_framework.declarative import WorkflowFactory
|
|
from agent_framework.foundry import FoundryChatClient
|
|
from agent_framework.openai import OpenAIChatOptions
|
|
from azure.identity import AzureCliCredential
|
|
from dotenv import load_dotenv
|
|
from pydantic import BaseModel, Field
|
|
|
|
# Load environment variables from .env file
|
|
load_dotenv()
|
|
|
|
# Agent Instructions
|
|
RESEARCH_INSTRUCTIONS = """In order to help begin addressing the user request, please answer the following pre-survey to the best of your ability.
|
|
Keep in mind that you are Ken Jennings-level with trivia, and Mensa-level with puzzles, so there should be a deep well to draw from.
|
|
|
|
Here is the pre-survey:
|
|
|
|
1. Please list any specific facts or figures that are GIVEN in the request itself. It is possible that there are none.
|
|
2. Please list any facts that may need to be looked up, and WHERE SPECIFICALLY they might be found. In some cases, authoritative sources are mentioned in the request itself.
|
|
3. Please list any facts that may need to be derived (e.g., via logical deduction, simulation, or computation)
|
|
4. Please list any facts that are recalled from memory, hunches, well-reasoned guesses, etc.
|
|
|
|
When answering this survey, keep in mind that 'facts' will typically be specific names, dates, statistics, etc. Your answer must only use the headings:
|
|
|
|
1. GIVEN OR VERIFIED FACTS
|
|
2. FACTS TO LOOK UP
|
|
3. FACTS TO DERIVE
|
|
4. EDUCATED GUESSES
|
|
|
|
DO NOT include any other headings or sections in your response. DO NOT list next steps or plans until asked to do so.""" # noqa: E501
|
|
|
|
PLANNER_INSTRUCTIONS = """Your only job is to devise an efficient plan that identifies (by name) how a team member may contribute to addressing the user request.
|
|
|
|
Only select the following team which is listed as "- [Name]: [Description]"
|
|
|
|
- WeatherAgent: Able to retrieve weather information
|
|
- CoderAgent: Able to write and execute Python code
|
|
- KnowledgeAgent: Able to perform generic websearches
|
|
|
|
The plan must be a bullet point list must be in the form "- [AgentName]: [Specific action or task for that agent to perform]"
|
|
|
|
Remember, there is no requirement to involve the entire team -- only select team member's whose particular expertise is required for this task.""" # noqa: E501
|
|
|
|
MANAGER_INSTRUCTIONS = """Recall we have assembled the following team:
|
|
|
|
- KnowledgeAgent: Able to perform generic websearches
|
|
- CoderAgent: Able to write and execute Python code
|
|
- WeatherAgent: Able to retrieve weather information
|
|
|
|
To make progress on the request, please answer the following questions, including necessary reasoning:
|
|
- Is the request fully satisfied? (True if complete, or False if the original request has yet to be SUCCESSFULLY and FULLY addressed)
|
|
- Are we in a loop where we are repeating the same requests and / or getting the same responses from an agent multiple times? Loops can span multiple turns, and can include repeated actions like scrolling up or down more than a handful of times.
|
|
- Are we making forward progress? (True if just starting, or recent messages are adding value. False if recent messages show evidence of being stuck in a loop or if there is evidence of significant barriers to success such as the inability to read from a required file)
|
|
- Who should speak next? (select from: KnowledgeAgent, CoderAgent, WeatherAgent)
|
|
- What instruction or question would you give this team member? (Phrase as if speaking directly to them, and include any specific information they may need)""" # noqa: E501
|
|
|
|
SUMMARY_INSTRUCTIONS = """We have completed the task.
|
|
|
|
Based only on the conversation and without adding any new information,
|
|
synthesize the result of the conversation as a complete response to the user task.
|
|
|
|
The user will only ever see this last response and not the entire conversation,
|
|
so please ensure it is complete and self-contained."""
|
|
|
|
KNOWLEDGE_INSTRUCTIONS = """You are a knowledge agent that can perform web searches to find information."""
|
|
|
|
CODER_INSTRUCTIONS = """You solve problems by writing and executing code."""
|
|
|
|
WEATHER_INSTRUCTIONS = """You are a weather expert that can provide weather information."""
|
|
|
|
|
|
# Pydantic models for structured outputs
|
|
class ReasonedAnswer(BaseModel):
|
|
"""A response with reasoning and answer."""
|
|
|
|
reason: str = Field(description="The reasoning behind the answer")
|
|
answer: bool = Field(description="The boolean answer")
|
|
|
|
|
|
class ReasonedStringAnswer(BaseModel):
|
|
"""A response with reasoning and string answer."""
|
|
|
|
reason: str = Field(description="The reasoning behind the answer")
|
|
answer: str = Field(description="The string answer")
|
|
|
|
|
|
class ManagerResponse(BaseModel):
|
|
"""Response from manager agent evaluation."""
|
|
|
|
is_request_satisfied: ReasonedAnswer = Field(description="Whether the request is fully satisfied")
|
|
is_in_loop: ReasonedAnswer = Field(description="Whether we are in a loop repeating the same requests")
|
|
is_progress_being_made: ReasonedAnswer = Field(description="Whether forward progress is being made")
|
|
next_speaker: ReasonedStringAnswer = Field(description="Who should speak next")
|
|
instruction_or_question: ReasonedStringAnswer = Field(
|
|
description="What instruction or question to give the next speaker"
|
|
)
|
|
|
|
|
|
async def main() -> None:
|
|
"""Run the deep research workflow."""
|
|
# Create Azure OpenAI client
|
|
client = FoundryChatClient(
|
|
project_endpoint=os.environ["FOUNDRY_PROJECT_ENDPOINT"],
|
|
model=os.environ["FOUNDRY_MODEL"],
|
|
credential=AzureCliCredential(),
|
|
)
|
|
|
|
# Create agents
|
|
research_agent = Agent(
|
|
client=client,
|
|
name="ResearchAgent",
|
|
instructions=RESEARCH_INSTRUCTIONS,
|
|
)
|
|
|
|
planner_agent = Agent(
|
|
client=client,
|
|
name="PlannerAgent",
|
|
instructions=PLANNER_INSTRUCTIONS,
|
|
)
|
|
|
|
manager_agent = Agent(
|
|
client=client,
|
|
name="ManagerAgent",
|
|
instructions=MANAGER_INSTRUCTIONS,
|
|
default_options=OpenAIChatOptions[Any](response_format=ManagerResponse),
|
|
)
|
|
|
|
summary_agent = Agent(
|
|
client=client,
|
|
name="SummaryAgent",
|
|
instructions=SUMMARY_INSTRUCTIONS,
|
|
)
|
|
|
|
knowledge_agent = Agent(
|
|
client=client,
|
|
name="KnowledgeAgent",
|
|
instructions=KNOWLEDGE_INSTRUCTIONS,
|
|
)
|
|
|
|
coder_agent = Agent(
|
|
client=client,
|
|
name="CoderAgent",
|
|
instructions=CODER_INSTRUCTIONS,
|
|
)
|
|
|
|
weather_agent = Agent(
|
|
client=client,
|
|
name="WeatherAgent",
|
|
instructions=WEATHER_INSTRUCTIONS,
|
|
)
|
|
|
|
# Create workflow factory
|
|
factory = WorkflowFactory(
|
|
agents={
|
|
"ResearchAgent": research_agent,
|
|
"PlannerAgent": planner_agent,
|
|
"ManagerAgent": manager_agent,
|
|
"SummaryAgent": summary_agent,
|
|
"KnowledgeAgent": knowledge_agent,
|
|
"CoderAgent": coder_agent,
|
|
"WeatherAgent": weather_agent,
|
|
},
|
|
)
|
|
|
|
# Load workflow from YAML
|
|
samples_root = Path(__file__).parent.parent.parent.parent.parent.parent
|
|
workflow_path = samples_root / "declarative-agents" / "workflow-samples" / "DeepResearch.yaml"
|
|
if not workflow_path.exists():
|
|
# Fall back to local copy if declarative-agents/workflow-samples doesn't exist
|
|
workflow_path = Path(__file__).parent / "workflow.yaml"
|
|
|
|
workflow = factory.create_workflow_from_yaml_path(workflow_path)
|
|
|
|
print(f"Loaded workflow: {workflow.name}")
|
|
print("=" * 60)
|
|
print("Deep Research Workflow (Magentic Pattern)")
|
|
print("=" * 60)
|
|
|
|
# Example input
|
|
task = "What is the weather like in Seattle and how does it compare to the average for this time of year?"
|
|
|
|
async for event in workflow.run(task, stream=True):
|
|
if event.type == "output":
|
|
print(f"\n{event.data}", flush=True)
|
|
|
|
print("\n" + "=" * 60)
|
|
print("Research Complete")
|
|
print("=" * 60)
|
|
|
|
|
|
if __name__ == "__main__":
|
|
asyncio.run(main())
|