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

{
The right issue is harder because it spans authentication middleware, standards-compliant discovery endpoints, external identity-provider configuration, client interoperability, and security-focused testing. The left issue is comparatively contained within provider registration, model metadata, request translation, and pricing integration.
}
https://github.com/berriai/litellm/issues/31296 3:1 https://github.com/berriai/litellm/issues/31568

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

{
30421 spans a new CLI workflow, multiple third-party agent integrations, remote model discovery, credential handling, and cross-platform process/configuration behavior. 31296 is comparatively bounded to protocol-compliant metadata and authentication response handling within existing MCP middleware, with focused tests.
}
https://github.com/berriai/litellm/issues/30421 5:2 https://github.com/berriai/litellm/issues/31296

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

{
26535 requires broader cross-provider validation, matrix expansion, CI integration, and coordination across multiple implementation slices, creating substantially more engineering and maintenance risk than the focused authentication endpoint and metadata feature in 31296.
}
https://github.com/berriai/litellm/issues/26535 3:2 https://github.com/berriai/litellm/issues/31296

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

{
Issue 34328 is harder because it requires correcting recursive schema expansion safely, preserving translation behavior, enforcing budgets across multiple provider paths, and validating CPU/memory termination under adversarial schemas. Issue 31296 is a more bounded authentication-discovery feature involving endpoint behavior, metadata configuration, and response integration.
}
https://github.com/berriai/litellm/issues/34328 3:1 https://github.com/berriai/litellm/issues/31296

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

{
Issue #31296 is harder because it introduces a new inbound authentication and standards-compliance flow spanning proxy routing, OAuth metadata discovery, configuration, response semantics, and security-focused integration tests. Issue #26897 is narrower, centered on diagnosing and correcting parameter propagation or Azure URL construction in an existing Responses bridge path.
}
https://github.com/berriai/litellm/issues/31296 3:1 https://github.com/berriai/litellm/issues/26897

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

{
The left task spans a new quota metric, calendar-based and timezone-aware lifecycle handling, overflow and warning semantics, enforcement, persistence, and coordinated API/UI exposure. The right task primarily extends existing budget-window, reservation, counter, and reset infrastructure to another entity scope, with concurrency and migration considerations but less new surface area.
}
https://github.com/berriai/litellm/issues/31821 5:4 https://github.com/berriai/litellm/issues/28235

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

{
Issue 29452 is harder because it requires a cross-cutting authentication and secret-storage abstraction with provider compatibility, credential lifecycle handling, and security-sensitive integration. Issue 30460 is a narrower but risky distributed-state debugging and correction effort.
}
https://github.com/berriai/litellm/issues/29452 3:2 https://github.com/berriai/litellm/issues/30460

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

{
The left requires coordinated changes across request enforcement, durable usage accounting, concurrency safety, time-window semantics, APIs, and UI, creating substantially broader integration and migration risk. The right is primarily an authentication abstraction and provider-integration effort, with narrower runtime and data-consistency impact.
}
https://github.com/berriai/litellm/issues/31821 3:1 https://github.com/berriai/litellm/issues/29452

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

{
Issue 32201 is harder because it requires integrating enforcement into pass-through response processing, including raw/streaming formats and guardrail execution paths, while issue 31296 is a more bounded authentication-metadata and response-header addition.
}
https://github.com/berriai/litellm/issues/32201 3:1 https://github.com/berriai/litellm/issues/31296

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

{
#34328 is harder because it requires correcting recursive schema expansion safeguards across multiple provider translation paths, addressing algorithmic termination and resource limits, and validating complex performance regressions. #32201 is narrower endpoint/response-processing integration work with a more localized enforcement fix.
}
https://github.com/berriai/litellm/issues/34328 3:1 https://github.com/berriai/litellm/issues/32201