You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by ka...@apache.org on 2026/10/14 01:48:02 UTC
(airflow) branch commonai-why-pydantic-ai created (now 13cc0f4d02c)
This is an automated email from the ASF dual-hosted git repository.
kaxil pushed a change to branch commonai-why-pydantic-ai
in repository https://gitbox.apache.org/repos/asf/airflow.git
at 13cc0f4d02c Explain why common.ai is built on Pydantic AI
This branch includes the following new commits:
new 13cc0f4d02c Explain why common.ai is built on Pydantic AI
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(airflow) 01/01: Explain why common.ai is built on Pydantic AI
Posted by ka...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
kaxil pushed a commit to branch commonai-why-pydantic-ai
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 13cc0f4d02cb23af2082818c74de75922261f43a
Author: Kaxil Naik <ka...@apache.org>
AuthorDate: Wed Oct 14 02:38:14 2026 +0100
Explain why common.ai is built on Pydantic AI
Say what Pydantic AI gives a Dag (no vendor or cloud lock-in, typed output,
tests without a model, tool approval), recommend AgentOperator for new
agents, and keep Strands, ADK and LangChain as supported routes.
---
providers/common/ai/docs/frameworks/index.rst | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/providers/common/ai/docs/frameworks/index.rst b/providers/common/ai/docs/frameworks/index.rst
index e99537b90a7..912ce9d4eab 100644
--- a/providers/common/ai/docs/frameworks/index.rst
+++ b/providers/common/ai/docs/frameworks/index.rst
@@ -26,6 +26,33 @@ another framework, you do not have to move them to Pydantic AI to run them in Ai
Run the agent in a ``@task`` as you do today, and use this provider for the parts that
need Airflow: models and tools backed by Airflow connections.
+Why Pydantic AI
+---------------
+
+An Airflow deployment runs on whichever cloud and model vendor its team chose, and the
+same Dags often outlive that choice. The provider's own operators are built on Pydantic
+AI because it does not tie a Dag to either:
+
+- **No vendor or cloud to commit to.** The same operator reaches OpenAI, Anthropic,
+ Gemini, Vertex AI, Bedrock, Azure OpenAI, Mistral, Groq, DeepSeek and self-hosted
+ OpenAI-compatible servers such as Ollama and vLLM, through an Airflow connection.
+ Moving a Dag to another vendor is a connection change, not a code change. See
+ :doc:`../model_providers`.
+- **Typed output.** ``output_type`` makes the agent return a Pydantic model, so the
+ task downstream gets fields to read instead of text to parse. See
+ :doc:`../structured_output`.
+- **Tests that do not call a model.** A connection whose model is ``test`` runs the Dag
+ against Pydantic AI's ``TestModel``, and a unit test can script the model's replies.
+ Neither calls a model provider or spends tokens. See :doc:`../local_development`.
+- **A pause before a tool acts.** Pydantic AI's tool approval API is what lets
+ ``AgentOperator`` stop in front of a marked tool call until a person approves it. See
+ :doc:`../tool_approval`.
+
+Pydantic AI is the recommendation, not a requirement. For a new agent, start with
+``AgentOperator``, which gets the most from this provider. If your team has standardized
+on Strands, ADK or LangChain, keep that framework: the table below shows what this
+provider gives an agent written in each one.
+
Supported frameworks
--------------------