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

{
The right issue is harder because it involves tracing timeout propagation through provider-specific streaming control flow, iterator lifecycle, and regression coverage across streaming and non-streaming paths. The left issue is more localized to content normalization and targeted prompt-mapping tests.
}
https://github.com/berriai/litellm/issues/26939 3:1 https://github.com/berriai/litellm/issues/32904

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

{
The left requires tracing request-scoped context through MCP authentication resolution and transport forwarding, with precedence and integration-test risks. The right is comparatively localized control-flow and state-isolation work around an existing polling loop.
}
https://github.com/berriai/litellm/issues/35403 3:2 https://github.com/berriai/litellm/issues/35357

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

{
The left issue is harder because it spans shared Pydantic model composition, provider-specific configuration semantics, initialization flow, and compatibility testing. The right issue is comparatively localized to a transformation branch with focused regression coverage, though it still carries some API-compatibility risk.
}
https://github.com/berriai/litellm/issues/32061 3:1 https://github.com/berriai/litellm/issues/34978

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

{
The right-hand task is harder because it crosses provider-specific multimodal request handling, response normalization, usage accounting, and compatibility tests. The left-hand task is comparatively localized parameter propagation across existing transformation paths, with narrower behavioral risk.
}
https://github.com/berriai/litellm/issues/33681 4:3 https://github.com/berriai/litellm/issues/28132

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

{
The Azure integration requires provider-specific capability analysis, request translation, compatibility handling, and broader testing across affected request and billing paths. The video issue is more localized, requiring coordinated metadata resolution changes across several endpoints plus regression coverage.
}
https://github.com/berriai/litellm/issues/27529 3:2 https://github.com/berriai/litellm/issues/33740

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

{
Issue #24235 is harder because it requires defining and applying billing-exclusion semantics across usage aggregation, BYOK classification, reporting behavior, and regression coverage, with a higher risk of affecting financial correctness. Issue #32596 appears more localized to correcting duplicate persistence behavior in an existing managed-batch retrieval path.
}
https://github.com/berriai/litellm/issues/24235 3:2 https://github.com/berriai/litellm/issues/32596

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

{
32614 is harder because it requires correcting asynchronous coordination and cache-consistency behavior across shared proxy budget paths, with concurrency-sensitive regression testing; 25688 is comparatively localized to exposing and wiring a provider configuration choice in the dashboard.
}
https://github.com/berriai/litellm/issues/32614 4:1 https://github.com/berriai/litellm/issues/25688

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

{
33440 requires new configuration plumbing, runtime default handling, compatibility considerations, and behavioral tests, while 29011 is primarily bounded metadata validation and data-file corrections.
}
https://github.com/berriai/litellm/issues/33440 3:1 https://github.com/berriai/litellm/issues/29011

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

{
The dashboard work requires tracing configuration data through rendering and clipboard-generation paths, handling UI state and validation, and adding coverage; the endpoint fix is comparatively localized to routing behavior with focused regression testing.
}
https://github.com/berriai/litellm/issues/30468 3:1 https://github.com/berriai/litellm/issues/33676

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

{
The left issue is harder because it involves diagnosing and correcting cross-provider request translation in a proxy integration, with compatibility behavior and end-to-end client testing. The right issue is primarily structured metadata correction and coverage expansion, requiring broader data validation but less runtime integration work.
}
https://github.com/berriai/litellm/issues/26214 3:2 https://github.com/berriai/litellm/issues/35011