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

{
#32247 is harder because it involves concurrent cache invalidation, mutable shared authentication state, and preventing stale writes without introducing authorization or spend-tracking regressions. #32575 is comparatively localized to lifecycle initialization and synchronization of persisted MCP state with its runtime registry.
}
https://github.com/berriai/litellm/issues/32247 5:3 https://github.com/berriai/litellm/issues/32575

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

{
#35097 is harder because it requires router-wide semantic changes, request-level option handling, candidate selection and fallback behavior, plus compatibility and regression testing. #33516 appears comparatively localized and primarily diagnostic.
}
https://github.com/berriai/litellm/issues/35097 4:1 https://github.com/berriai/litellm/issues/33516

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

{
Provider-specific metadata propagation requires tracing multiple request and spend-logging paths, handling compatibility concerns, and adding regression coverage; the other is primarily synchronized model-catalog data maintenance.
}
https://github.com/berriai/litellm/issues/29079 4:1 https://github.com/berriai/litellm/issues/24229

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

{
The right-side issue is harder because it affects asynchronous control flow, exception translation, endpoint response semantics, and compatibility across hook consumers, requiring broader integration testing. The left-side issue is comparatively localized to database hydration and reuse of existing configuration-resolution behavior.
}
https://github.com/berriai/litellm/issues/35543 3:1 https://github.com/berriai/litellm/issues/32677

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

{
The left issue is harder because it requires isolating a potentially workload-dependent memory regression, profiling background database and cleanup behavior, reproducing it under realistic deployment conditions, and validating a safe fix without introducing operational instability. The right issue is narrower and likely permits a localized identity-reconciliation change with focused authentication, persistence, and authorization tests.
}
https://github.com/berriai/litellm/issues/25219 3:1 https://github.com/berriai/litellm/issues/28537

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

{
#33397 is harder because it affects authorization semantics across multiple principal types, configuration persistence, dashboard behavior, and backward-compatibility expectations. #33988 is comparatively localized to making a retrieval hook idempotent and adding focused regression coverage.
}
https://github.com/berriai/litellm/issues/33397 3:1 https://github.com/berriai/litellm/issues/33988

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

{
31510 requires security-sensitive guardrail coverage across multiple request schemas, shared extraction logic, and broader regression testing; 30126 is more localized request-path/logging integration work.
}
https://github.com/berriai/litellm/issues/31510 3:2 https://github.com/berriai/litellm/issues/30126

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

{
Issue #33344 requires cross-layer debugging of request propagation, compatibility analysis, security-sensitive behavior, and regression testing; #28338 mainly tracks already-proposed implementation work.
}
https://github.com/berriai/litellm/issues/33344 5:1 https://github.com/berriai/litellm/issues/28338

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

{
The right issue is harder because it involves intermittent, cross-provider multimodal translation behavior, requiring careful request normalization, regression coverage, and validation of token accounting without breaking audio handling. The left issue is more contained: integrating existing database-view creation into the migration lifecycle and verifying permissions and startup behavior.
}
https://github.com/berriai/litellm/issues/29138 3:1 https://github.com/berriai/litellm/issues/28162

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

{
Issue 32193 is substantially harder: it requires designing a general configuration and SDK contract, implementing provider-agnostic matching and transformation logic across varied error paths, handling streaming and sensitive-data safety, and preserving compatibility across proxy and client surfaces. Issue 27048 is comparatively localized to diagnosing and correcting a frontend static-export route/build integration.
}
https://github.com/berriai/litellm/issues/32193 5:1 https://github.com/berriai/litellm/issues/27048