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

{
MCP compatibility requires deeper protocol, session, routing, and client-interoperability investigation, with greater regression risk. The UI problem is more localized to frontend static-export/build configuration and should have a narrower validation surface.
}
https://github.com/berriai/litellm/issues/31179 3:1 https://github.com/berriai/litellm/issues/27048

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

{
The right issue is harder because it requires tracing and extending a provider-specific multipart request path, validating parameter mappings and upstream compatibility, and adding integration coverage. The left issue is a localized conditional fix with focused regression tests.
}
https://github.com/berriai/litellm/issues/28636 4:1 https://github.com/berriai/litellm/issues/29283

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

{
#26167 is harder due to cross-layer Responses-to-chat translation, persistence/session reconstruction, identifier consistency, and multi-turn tool-call behavior. #33026 is comparatively localized to error propagation and HTTP status mapping on one endpoint.
}
https://github.com/berriai/litellm/issues/26167 4:1 https://github.com/berriai/litellm/issues/33026

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/32557 3:1 https://github.com/berriai/litellm/issues/30725

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

{
Enabling outbound HTTP/2 safely requires cross-cutting client, transport, dependency, configuration, and compatibility work across many provider paths. The other issue is narrower, centered on correcting an async streaming boundary in one emulated-tool flow.
}
https://github.com/berriai/litellm/issues/30362 4:1 https://github.com/berriai/litellm/issues/34767

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

{
The right issue is harder because it requires tracing and correcting model-resolution behavior across fallback routing, team scoping, and backward-compatible tests. The left issue is primarily a narrowly scoped chart dependency/version maintenance change.
}
https://github.com/berriai/litellm/issues/28019 4:1 https://github.com/berriai/litellm/issues/26169

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

{
Issue #32221 is harder because it spans multiple synchronous and asynchronous retry paths and must preserve correct exception propagation, HTTP status handling, spend logging, callbacks, and router fallback behavior. Issue #31838 is comparatively localized to adding Redis cache invalidation across customer mutation endpoints and covering it with targeted tests.
}
https://github.com/berriai/litellm/issues/32221 4:1 https://github.com/berriai/litellm/issues/31838

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

{
The harder task spans proxy configuration, telemetry pipeline behavior, sampling semantics, backward compatibility, and integration tests; the other is a narrower provider-translation validation and remediation change.
}
https://github.com/berriai/litellm/issues/30939 3:1 https://github.com/berriai/litellm/issues/19384

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

{
The right issue is harder because it spans container-image layout, filesystem permissions, migration tooling, and Kubernetes/Helm job behavior, whereas the left issue is primarily a localized guardrail-dispatch and configuration-propagation fix with targeted tests.
}
https://github.com/berriai/litellm/issues/26918 3:1 https://github.com/berriai/litellm/issues/34922

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

{
The right issue is harder because it spans provider-specific request adaptation, tool-type compatibility, schema transformation, and regression coverage across multiple client protocols, while the left issue appears more localized to proxy image-generation request handling.
}
https://github.com/berriai/litellm/issues/31449 4:1 https://github.com/berriai/litellm/issues/30300