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

{
The right issue likely requires tracing configuration propagation across proxy, provider parameter handling, and AWS credential/role-assumption behavior, with integration and security-sensitive testing. The left issue appears more localized to exception classification and HTTP status mapping in one endpoint.
}
https://github.com/berriai/litellm/issues/25884 3:1 https://github.com/berriai/litellm/issues/34422

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

{
The right-hand issue likely requires broader protocol, proxy, and compatibility investigation across request parsing and streaming behavior, with higher regression risk. The left-hand issue is comparatively localized to defensive handling in an existing adapter plus focused tests.
}
https://github.com/berriai/litellm/issues/29818 3:1 https://github.com/berriai/litellm/issues/30761

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

{
Cancellation-safe persistence spans asynchronous task lifecycle, queue locking, failure recovery, shutdown behavior, and race-condition testing; the other is a narrower usage-normalization and accounting change across provider schemas.
}
https://github.com/berriai/litellm/issues/34820 3:2 https://github.com/berriai/litellm/issues/31594

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

{
The left issue is harder because it requires tracing provider usage normalization, cache-token accounting, pricing calculations, and reconciliation tests across logging and billing paths. The right issue appears more localized to request-header handling and encoding behavior, with a narrower compatibility-focused fix.
}
https://github.com/berriai/litellm/issues/34801 3:1 https://github.com/berriai/litellm/issues/34633

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

{
The right-side change spans proxy persistence, model-update mutation, router-specific state, and model-info filtering, requiring lifecycle tracing and regression coverage across API and database paths. The left-side change is more localized to the Anthropic token-counting adapter and shared request normalization, with narrower tests and lower integration risk.
}
https://github.com/berriai/litellm/issues/31694 5:3 https://github.com/berriai/litellm/issues/26324

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

{
The right-hand issue is harder because it spans provider-specific request adaptation, multiple client/API tool formats, unsupported tool semantics, schema compatibility, and regression coverage across several request paths. The left-hand issue is comparatively localized to preserving the selected deployment identity through cost and pricing lookup.
}
https://github.com/berriai/litellm/issues/31449 3:1 https://github.com/berriai/litellm/issues/28228

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

{
The left issue requires careful failure-state handling, atomicity guarantees, and regression coverage across multiple budget-counter paths; the right is primarily a provider-parameter translation and compatibility change.
}
https://github.com/berriai/litellm/issues/35569 4:1 https://github.com/berriai/litellm/issues/27529

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

{
#24987 requires tracing provider-specific request translation and cache metadata across proxy/pass-through paths, with compatibility and regression testing; #32226 is more narrowly scoped to correcting byte-boundary handling and adding UTF-8 coverage.
}
https://github.com/berriai/litellm/issues/24987 3:1 https://github.com/berriai/litellm/issues/32226

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

{
OAuth/MCP authentication behavior spans middleware, protocol-specific challenge headers, and interactive-flow compatibility, creating greater integration and regression risk; the logging change is comparatively localized to logger filtering/configuration.
}
https://github.com/berriai/litellm/issues/29261 4:1 https://github.com/berriai/litellm/issues/10788

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

{
The left issue is harder because it requires provider-specific streaming aggregation, preservation of structured metadata across chunk boundaries, compatibility with existing non-streaming behavior, and regression coverage for multi-turn tool workflows. The right issue is primarily an export aggregation discrepancy, likely localized to dashboard query or grouping logic and easier to validate against existing totals.
}
https://github.com/berriai/litellm/issues/25869 3:1 https://github.com/berriai/litellm/issues/32581