Document when to use common.ai vs vendor-specific AI providers - #69551
Merged
Conversation
Lee-W
force-pushed
the
ai-provider-usage-docs
branch
2 times, most recently
from
July 8, 2026 04:40
df9954b to
feac1fd
Compare
Lee-W
marked this pull request as ready for review
July 8, 2026 06:05
Lee-W
force-pushed
the
ai-provider-usage-docs
branch
from
July 8, 2026 06:05
feac1fd to
36aa507
Compare
gopidesupavan
approved these changes
Jul 8, 2026
gopidesupavan
left a comment
gopidesupavan
left a comment
Member
There was a problem hiding this comment.
LGTM, thanks for adding..
The common.ai, openai, and anthropic docs landing pages now explain how to choose between the vendor-neutral operators and the native API wrappers — including where the agent loop runs (Airflow worker vs vendor-managed service).
Lee-W
force-pushed
the
ai-provider-usage-docs
branch
from
July 8, 2026 08:50
36aa507 to
d07db20
Compare
kaxil
reviewed
Jul 8, 2026
| When to use this provider | ||
| -------------------------- | ||
|
|
||
| ``common.ai`` is the vendor-neutral way to put LLM and agent steps in a Dag. It is built on |
Member
There was a problem hiding this comment.
A reader who already has LangChain or LlamaIndex code may read "built on pydantic-ai" as "not for me" and move on. Since the provider ships a LangChain toolset (the langchain extra), one sentence noting that existing LangChain tools can be called from a common.ai agent would keep that reader engaged, without overstating support.
Member
Author
There was a problem hiding this comment.
I added it to the middle of this paragraph in https://github.com/apache/airflow/pull/69649/changes. let me know if it's better to move it or extend it
1 task
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Jul 9, 2026
…docs Reviewer feedback on apache#69551 (merged) asked for a scannable package-choice table linking to the vendor provider pages, a note that existing LangChain tools work via the langchain extra, and a link to the toolsets doc from the agent bullet.
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Jul 9, 2026
…fy batch tradeoff Reviewer feedback on apache#69551 (merged) noted the comparison section ran before readers knew what the provider was, that OpenAIHook isn't batch-specific, and that the batch bullet didn't explain why one would pick it over a synchronous call.
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Jul 9, 2026
…d batch cost/turnaround rationale Reviewer feedback on apache#69551 (merged) noted the comparison section ran before readers knew what the provider was, and that the batch bullet didn't explain why one would pick it over a synchronous call. The new clause reuses the cost/turnaround figures already documented in operators/anthropic.rst for consistency.
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
3 participants
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.
Why
common.aioperators and each vendor's native API wrappers — readers had to infer it.What
common.ai,openai, andanthropicindex pages now each carry a "When to use this provider" section with the decision rule and a runnable example snippet.common.ai, model stays swappable via connection) vs submitted to a vendor-managed service (native Batch / Responses / Managed Agents endpoints).Was generative AI tooling used to co-author this PR?
Generated-by: [Claude] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.