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

{
Supporting a new provider request shape requires changes across request validation, translation, compatibility handling, and regression coverage, with higher risk of affecting multiple Claude paths. The cache defect is comparatively localized to deletion cleanup and key-format consistency, with focused tests.
}
https://github.com/berriai/litellm/issues/25073 3:1 https://github.com/berriai/litellm/issues/34217

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

{
The right-hand task is harder because it requires tracing model identity through Azure router selection and the spend-logging pipeline, preserving consistency across response metadata, callbacks, and persistence, with broader regression-testing risk. The left-hand task is a narrowly scoped retry-parameter propagation fix with an established pattern to follow.
}
https://github.com/berriai/litellm/issues/27942 4:1 https://github.com/berriai/litellm/issues/27363

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

{
The right-hand feature has broader architectural scope across configuration schema, proxy integration, persistence, validation, and backward compatibility, while the left-hand bug appears localized to fallback resolution and regression coverage.
}
https://github.com/berriai/litellm/issues/27287 3:1 https://github.com/berriai/litellm/issues/35578

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

{
The right issue is harder because it combines cross-cutting usage attribution with a substantial new provider API integration, requiring design work across request handling, identity propagation, accounting, compatibility, and testing. The left issue is comparatively localized to model capability detection, parameter filtering, and regression coverage.
}
https://github.com/berriai/litellm/issues/32225 4:1 https://github.com/berriai/litellm/issues/33171

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

{
30635 is harder because it requires tracing and safely repairing authentication context across background scheduling, router retrieval, enterprise hooks, resource isolation, and spend accounting, with regression coverage across managed batch flows. 35383 is comparatively narrower: adjusting ownership identity and configurable limits within the MCP session-management path, though it still needs concurrency and compatibility tests.
}
https://github.com/berriai/litellm/issues/30635 5:3 https://github.com/berriai/litellm/issues/35383

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

{
The left requires cross-cutting identity reconciliation, compatibility handling, and regression coverage across authentication and authorization paths; the right is a localized provider-metadata/UI consistency fix.
}
https://github.com/berriai/litellm/issues/28537 5:1 https://github.com/berriai/litellm/issues/27384

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

{
The left task is harder because it requires diagnosing an elusive latency regression across provider translation, streaming behavior, authentication, retries, and deployment boundaries. The right task is a broader feature integration, but its interfaces and validation flow can be designed and tested more directly.
}
https://github.com/berriai/litellm/issues/26699 3:2 https://github.com/berriai/litellm/issues/26514

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

{
32973 requires coordinated compatibility logic across multiple request pathways, provider adapters, model generations, and regression tests, creating substantially broader scope and integration risk. 22159 is comparatively localized to initialization and lazy-loading behavior, with narrower testing and rollout concerns.
}
https://github.com/berriai/litellm/issues/32973 4:1 https://github.com/berriai/litellm/issues/22159

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

{
The left issue spans provider capability mapping, multimodal request handling, and possible upstream compatibility constraints, requiring broader investigation and integration testing. The right issue appears localized to configuration propagation during router reconstruction, with a more targeted code change and regression test.
}
https://github.com/berriai/litellm/issues/27083 3:1 https://github.com/berriai/litellm/issues/32106

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

{
The left requires UI integration, dynamic command construction, transport and header edge-case handling, and validation; the right is a narrowly scoped synchronized metadata change.
}
https://github.com/berriai/litellm/issues/30470 3:1 https://github.com/berriai/litellm/issues/32046