Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
Streaming error semantics require tracing asynchronous event translation, preserving exception behavior across SDK layers, and adding regression coverage without breaking valid terminal events. The embedding defect is more localized response-shape normalization, though it spans two adapter paths and needs compatibility tests.
}
https://github.com/berriai/litellm/issues/29223 3:2 https://github.com/berriai/litellm/issues/30004

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right issue is harder because it introduces a cross-cutting observability integration, external service interaction, configuration, metric enrichment, and compatibility across multiple callback backends. The left is technically sensitive but more contained within realtime routing and WebSocket transport handling.
}
https://github.com/berriai/litellm/issues/31226 5:4 https://github.com/berriai/litellm/issues/31613

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The left issue is harder because it involves diagnosing a regression in a provider-specific image-generation integration across multiple model variants and API behaviors, with greater external-service and compatibility uncertainty. The right issue appears more localized to shared parameter-routing logic, with a clearer implementation path and narrower test surface.
}
https://github.com/berriai/litellm/issues/19334 3:1 https://github.com/berriai/litellm/issues/26443

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The left issue spans provider-specific message translation, server-tool ID generation, multi-turn state consistency, and regression coverage across multiple interception paths. The right issue is a localized metadata merge correction with comparatively limited behavioral scope.
}
https://github.com/berriai/litellm/issues/31569 5:1 https://github.com/berriai/litellm/issues/27134

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right issue spans configuration, timezone-aware aggregation and filtering, exports, and UI consistency, creating broader cross-layer changes and edge-case risk. The left issue is comparatively localized to stream block serialization with targeted compatibility tests.
}
https://github.com/berriai/litellm/issues/31831 4:1 https://github.com/berriai/litellm/issues/35333

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
Issue 34619 is harder because it requires broad provider-integration work across model discovery, endpoint mapping, request/response transformations, compatibility handling, and comprehensive testing. Issue 33456 is more likely a localized streaming-serialization compatibility fix.
}
https://github.com/berriai/litellm/issues/34619 3:1 https://github.com/berriai/litellm/issues/33456

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The left issue requires diagnosing and safely correcting asynchronous cancellation, state initialization, protocol-specific behavior, and regression coverage across MCP transport variants. The right issue appears more localized to proxy callback wiring and should be easier to isolate and fix.
}
https://github.com/berriai/litellm/issues/24089 5:2 https://github.com/berriai/litellm/issues/29638

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
#28019 requires broader routing-path changes and cross-scope compatibility validation, while #34905 is a localized metadata-merge correction with focused tests.
}
https://github.com/berriai/litellm/issues/28019 4:1 https://github.com/berriai/litellm/issues/34905

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right issue requires provider-specific capability logic, model identification, request-parameter filtering, and regression coverage, carrying compatibility risk across multiple model variants. The left issue is a localized layout and interaction adjustment in the dashboard.
}
https://github.com/berriai/litellm/issues/26444 4:1 https://github.com/berriai/litellm/issues/28679

Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The telemetry issue is harder because it crosses instrumentation, data-shape conversion, OpenTelemetry compatibility, and regression testing across tracing paths. The dependency issue is comparatively contained: update optional dependencies and add targeted configuration/startup validation with packaging tests.
}
https://github.com/berriai/litellm/issues/24057 3:1 https://github.com/berriai/litellm/issues/30320