+1 from me πŸ™Œ
As a regular Anthropic user, I'd be happy to help with reviews or testing
if needed.

Thanks,
Yeonguk

2026λ…„ 6μ›” 26일 (금) μ˜€μ „ 10:25, Vikram Koka via dev <[email protected]>λ‹˜μ΄
μž‘μ„±:

> +1 on this without any hesitation.
>
> This has been a gap in Airflow even with the introduction of the Common AI
> provider.
> The Open AI provider has existed for a while now and fills a critical gap.
> Happy to help on this as needed.
>
> Vikram
>
>
>
>
>
> On Thu, Jun 25, 2026 at 5:13β€―PM Kaxil Naik <[email protected]> wrote:
>
> > Hi Airflow community,
> >
> > I'd like to propose adding a new community provider for Anthropic's
> Claude
> > API: apache-airflow-providers-anthropic.
> >
> > Integration overview
> > ---------------------------
> > Claude is a widely used family of LLMs accessed through the official
> > "anthropic" Python SDK. The provider lets Dag authors call Claude through
> > Airflow connections and operators rather than embedding SDK calls and API
> > keys in task code. It includes:
> >
> > - A hook that builds the right client for the configured platform (the
> >   first-party Anthropic API, Amazon Bedrock, Google Vertex AI, Claude
> >   Platform on AWS, and Microsoft Foundry), including keyless Workload
> >   Identity Federation.
> > - A deferrable Message Batches operator, sensor, and trigger for the
> >   asynchronous, lower-cost batch workflow (submit, defer, collect).
> > - A deferrable Managed Agents session operator and trigger for
> Anthropic's
> >   server-run agent sessions.
> >
> > It targets Airflow 3+ and would ship as incubation. It is intentionally a
> > separate
> > provider rather than part of common.ai: common.ai is a provider-agnostic
> > abstraction, whereas this exposes Anthropic-specific surfaces (Message
> > Batches, Managed Agents, token counting, the platform clients) that do
> not
> > fit a neutral interface. The two are complementary.
> >
> >
> > Working implementation
> > ---------------------------------
> > https://github.com/apache/airflow/pull/69003
> >
> >
> > I am happy to steward and
> > sponsor; I know Pavan would too, and if another committer would like to
> > co-steward this provider, please let me know.
> >
> > Thanks,
> > Kaxil
> >
>

Reply via email to