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

{
The right issue is harder because it involves security-sensitive authorization semantics, compatibility with existing key-edit flows, regression coverage, and careful distinction between omitted, unchanged, and intentionally modified fields. The left issue is more narrowly scoped to provider-specific endpoint and request handling.
}
https://github.com/berriai/litellm/issues/33277 3:1 https://github.com/berriai/litellm/issues/7275

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

{
The right issue is harder because it requires broader core response-normalization and exception/status propagation changes across provider integrations, with greater regression risk. The left issue is comparatively localized to one provider’s streaming transformation and targeted error handling.
}
https://github.com/berriai/litellm/issues/33148 3:1 https://github.com/berriai/litellm/issues/33622

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

{
The session feature spans authentication architecture, client activity tracking, sliding expiration, persistence, and security-sensitive edge cases. The budget bug is more localized to credential-rotation state handling and regression tests.
}
https://github.com/berriai/litellm/issues/28237 3:2 https://github.com/berriai/litellm/issues/31079

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

{
The left issue spans cross-provider request translation and preserves nuanced conversational semantics across Anthropic and vLLM pathways, requiring careful compatibility testing. The right issue is a narrower provider-specific parameter mapping and capability change with a smaller implementation surface.
}
https://github.com/berriai/litellm/issues/28580 3:1 https://github.com/berriai/litellm/issues/27529

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

{
25402 requires code changes across fallback handling and Responses API metadata propagation, with regression testing across routes and providers; 29295 is an informational outreach item requiring no implementation.
}
https://github.com/berriai/litellm/issues/25402 8:1 https://github.com/berriai/litellm/issues/29295

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

{
Semantic filtering spans MCP integration, tool selection, schema reconstruction, and provider-compatible translation, requiring broader investigation and regression coverage. The other issue appears more localized to request-parameter filtering and provider adapter behavior.
}
https://github.com/berriai/litellm/issues/28766 4:1 https://github.com/berriai/litellm/issues/24549

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

{
Introducing a new typed exception requires tracing model-resolution failure paths, integrating it with LiteLLM's exception hierarchy and provider-specific behavior, and adding compatibility-focused tests. The guardrail issue is comparatively localized: correcting a key lookup and updating targeted tests, with limited behavioral surface.
}
https://github.com/berriai/litellm/issues/29146 3:1 https://github.com/berriai/litellm/issues/25487

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

{
#29539 is harder because it involves diagnosing provider-specific translation behavior and validating compatibility across proxy, Azure, and image-generation paths; #29400 has insufficient detail and appears substantially narrower in scope.
}
https://github.com/berriai/litellm/issues/29539 5:1 https://github.com/berriai/litellm/issues/29400

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

{
Issue #29320 is substantially harder: it requires a new opt-in compaction subsystem spanning proxy and SDK request paths, callback lifecycle integration, configuration precedence, provider/model execution, fail-open behavior, observability, persistence, headers, and broad testing. Issue #30118 is a narrowly scoped regression involving URL/forwarded-header handling and deployment-specific redirect behavior.
}
https://github.com/berriai/litellm/issues/29320 8:1 https://github.com/berriai/litellm/issues/30118

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

{
#30484 spans multiple subsystems, priorities, and regression-sensitive workstreams, requiring broad coordination and validation; #27835 is a narrower provider-integration change with limited scope.
}
https://github.com/berriai/litellm/issues/30484 10:1 https://github.com/berriai/litellm/issues/27835