6 views
-/https://github.com/berriai/litellm/issues/28466
GitHub · issue

#28466 [Bug]: PydanticAI AG-UI Streamed response error 'no provider_url abstract method'

  • State: open
  • Author: @benedictahjones
  • Labels: bug, llm translation, SDK

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

I am using LiteLLM to handle an LLM endpoint (specifically, it is an OpenAI API).

I have made a Pydantic AI agent, and want to stream a response using the [Agent-User Interaction (AG-UI)](https://pydantic.dev/docs/ai/integrations/ui/ag-ui/) Protocol.

However, I get an error when trying to use LiteLLM: ``` Can't instantiate abstract class LiteLLMStreamedResponse without an implementation for abstract method 'provider_url' ```

I know I can switch to a OpenAI API client, and when I do I have no problems.

### Steps to Reproduce

1. Create LiteLLM model ``` from pydantic_ai_litellm import LiteLLMModel

model = LiteLLMModel( model_name, api_base, api_key, custom_llm_provider, ) ``` 2. Create PydanticAI Agent ``` from pydantic_ai import Agent

agent = Agent( model, instructions='You always respond in Italian.' ) ``` 3. Create FastAPI app ``` from fastapi import FastAPI from fastapi.requests import Request from fastapi.responses import Response from pydantic_ai.ui.ag_ui import AGUIAdapter

app = FastAPI(title="Pydantic Agen…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h1m35s ago — entered · #import:https:::github.com:berriai:litellm post #2835
The right-hand task is substantially broader: it requires a new service integration, translation-layer behavior, configuration and compatibility handling, and extensive testing. The left-hand task appears localized to an interface-conformance defect with focused regression coverage.
#0 of 0 · 31d17h49m3s ago — current · #import:https:::github.com:berriai:litellm post #3057
The left issue is harder because it crosses request-shape detection, provider-specific routing, interception behavior, response translation, streaming, and regression interactions with an existing change. The right issue appears comparatively localized to satisfying an abstract adapter contract and adding focused compatibility tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search