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

{
The left issue is harder because it involves tracing provider-specific tool-call normalization and the server-side agent execution lifecycle, with greater risk of regressions across model routes and MCP behavior. The right issue is a comparatively contained dashboard presentation change involving existing assets and model-to-family mapping.
}
https://github.com/berriai/litellm/issues/31911 5:1 https://github.com/berriai/litellm/issues/35095

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

{
#32112 is harder because it involves diagnosing and eliminating cross-request mutable-state leakage in the proxy, preserving provider-specific parameter behavior, and adding concurrency-focused regression coverage. #8842 is comparatively localized to async router callback dispatch and hook handling.
}
https://github.com/berriai/litellm/issues/32112 4:1 https://github.com/berriai/litellm/issues/8842

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

{
Issue 27122 is harder because it requires coordinating test-environment initialization and potentially many existing test paths, with CI and import-order risks. Issue 35577 appears more localized to router upsert handling, validation, and regression coverage.
}
https://github.com/berriai/litellm/issues/27122 3:2 https://github.com/berriai/litellm/issues/35577

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

{
31609 is harder because it spans MCP request context, credential resolution, error handling, and compatibility across listing and invocation flows, requiring broader integration tests. 28379 is comparatively localized to Redis Cluster connection initialization and authentication wiring.
}
https://github.com/berriai/litellm/issues/31609 3:1 https://github.com/berriai/litellm/issues/28379

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

{
27550 requires a broad gateway-wide decisioning system spanning provider capabilities, policy configuration, reliability behavior, observability, and extensive integration testing. 31706 is comparatively bounded: exposing and normalizing model-discovery results across API bases, with authentication and provider-compatibility edge cases.
}
https://github.com/berriai/litellm/issues/27550 5:1 https://github.com/berriai/litellm/issues/31706

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

{
The left task requires coordinated asynchronous streaming changes, per-deployment configuration, timing behavior, and regression testing across proxy integrations. The right task is primarily provider/model configuration diagnosis with comparatively limited product-code scope.
}
https://github.com/berriai/litellm/issues/31865 5:1 https://github.com/berriai/litellm/issues/28422

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

{
#23339 is harder because it spans proxy routing, OAuth callback behavior, browser security constraints, and custom URI handling, requiring broader integration and compatibility work. #27512 is comparatively localized to request-retry transformation logic with focused regression coverage.
}
https://github.com/berriai/litellm/issues/23339 3:1 https://github.com/berriai/litellm/issues/27512

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

{
Cloudflare integration likely spans provider-specific request/response transformation, compatibility validation, and regression coverage, while the model-info problem appears more localized to persistence and serialization behavior.
}
https://github.com/berriai/litellm/issues/24065 3:2 https://github.com/berriai/litellm/issues/23345

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

{
The right issue is substantially harder: it involves security-sensitive request routing, input validation, SSRF risk assessment, and asynchronous context-lifecycle correctness across streaming behavior. The left issue is comparatively localized to configuration propagation and validation-path consistency.
}
https://github.com/berriai/litellm/issues/31889 5:1 https://github.com/berriai/litellm/issues/35177

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

{
The left issue is highly underspecified, so implementation would require broad diagnosis, reproduction, and scope discovery. The right issue has a concrete failure path and localized provider-response handling, making its fix more bounded and testable.
}
https://github.com/berriai/litellm/issues/34895 3:1 https://github.com/berriai/litellm/issues/30004