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

{
The right issue is harder because it requires tracing per-model limits through runtime spend tracking and authorization, handling budget state and edge cases without affecting existing enforcement. The left issue is comparatively localized to endpoint classification and control-plane routing behavior.
}
https://github.com/berriai/litellm/issues/31842 3:1 https://github.com/berriai/litellm/issues/27461

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

{
The right-hand feature spans a new CLI workflow, multiple external agent integrations, model discovery, authentication, configuration, and cross-platform testing. The left-hand bug is narrower, centered on diagnosing and correcting concurrency-limit enforcement and adding regression coverage.
}
https://github.com/berriai/litellm/issues/30421 4:1 https://github.com/berriai/litellm/issues/27900

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

{
The left issue is harder because it crosses request-type handling, spend-log serialization, configuration propagation, persistence behavior, and regression coverage. The right issue is more localized to model-key normalization and the associated pricing/UI path.
}
https://github.com/berriai/litellm/issues/34747 3:1 https://github.com/berriai/litellm/issues/27612

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

{
The right issue is harder because it requires tracing and correcting authentication middleware behavior across MCP request handling, OAuth challenge generation, error mapping, and client compatibility, with integration and regression testing. The left issue is a bounded metadata update affecting static pricing/context records with straightforward validation.
}
https://github.com/berriai/litellm/issues/29261 5:1 https://github.com/berriai/litellm/issues/28306

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

{
#32941 has unspecified scope and therefore carries greater discovery and implementation uncertainty, while #28854 appears narrowly bounded to pricing-key compatibility, calculator handling, and regression tests.
}
https://github.com/berriai/litellm/issues/32941 3:1 https://github.com/berriai/litellm/issues/28854

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

{
The left issue is harder because it requires cancellation-safe asynchronous request handling, reliable deferred accounting, provider-specific behavior, and regression coverage under disconnect races. The right issue is a more bounded authentication change involving session expiry state, activity tracking, and coordinated UI/API tests.
}
https://github.com/berriai/litellm/issues/13245 5:3 https://github.com/berriai/litellm/issues/28237

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

{
Preserving provider metadata through streaming requires tracing asynchronous chunk handling, aggregation, translation, and schema compatibility, with greater regression risk. The access-control correction is comparatively localized to model-visibility filtering and focused authorization tests.
}
https://github.com/berriai/litellm/issues/16021 5:3 https://github.com/berriai/litellm/issues/26420

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

{
Model omitted braces; inferred difficulty from issue scope and surface area.
}
https://github.com/berriai/litellm/issues/28870 3:1 https://github.com/berriai/litellm/issues/34102

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

{
#29142 is harder because it involves request isolation, mutable cache semantics, concurrency, authorization and budget correctness, plus broader regression coverage. #32330 is comparatively localized to preserving an SDK type discriminator and should require a smaller code and test change.
}
https://github.com/berriai/litellm/issues/29142 5:1 https://github.com/berriai/litellm/issues/32330

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

{
Issue #31889 is substantially harder: it spans security-sensitive routing behavior and asynchronous context lifecycle, requiring threat modeling, careful architectural changes, and concurrency-focused regression testing. Issue #33142 is comparatively narrow, involving a targeted permission-list update with straightforward validation.
}
https://github.com/berriai/litellm/issues/31889 5:1 https://github.com/berriai/litellm/issues/33142