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

{
The routing defect is harder because it involves diagnosing stateful selection logic, concurrency or timing behavior, rate-limit accounting, and regression testing across deployment-selection scenarios. The dashboard change is comparatively contained: extending existing aggregation and visualization data to include a model dimension.
}
https://github.com/berriai/litellm/issues/16060 3:1 https://github.com/berriai/litellm/issues/29627

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

{
The right-hand change is harder because it crosses the streaming response pipeline, requires preserving compatibility across event formats and clients, and needs broader integration and regression testing. The left-hand change is comparatively isolated to CLI argument handling, existing pricing utilities, and command-level tests.
}
https://github.com/berriai/litellm/issues/30816 3:2 https://github.com/berriai/litellm/issues/34686

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

{
Concurrent quota enforcement requires race-safe accounting, correct distributed behavior, and regression testing under load; the provider addition is comparatively localized to an adapter, request formatting, and basic validation.
}
https://github.com/berriai/litellm/issues/18730 5:1 https://github.com/berriai/litellm/issues/29570

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

{
The left issue is harder because it requires tracing a request option through proxy validation, provider-specific parameter translation, reasoning-generation behavior, and response normalization while preserving compatibility across models. The right issue is comparatively localized to an iterator’s accumulation strategy, with focused regression and performance tests.
}
https://github.com/berriai/litellm/issues/26413 4:1 https://github.com/berriai/litellm/issues/31861

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

{
Budget admission changes require designing safe semantics for unknown pricing across concurrent and distributed requests, preserving existing enforcement modes, and adding broad regression coverage. The streaming fix is narrower: contain the hook failure and emit a protocol-compliant terminal SSE response, mainly requiring careful async-generator and client-compatibility tests.
}
https://github.com/berriai/litellm/issues/35524 3:2 https://github.com/berriai/litellm/issues/26387

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

{
Issue 34614 is harder because it requires resolving a dependency/API compatibility problem across multiple Redis and Valkey code paths, including cache operations and budget accounting, with broader regression testing. Issue 32324 is a localized argument-plumbing correction with a narrower behavioral scope.
}
https://github.com/berriai/litellm/issues/34614 3:1 https://github.com/berriai/litellm/issues/32324

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

{
The left issue requires designing reusable batching, size-limit handling, configuration, retries, and integration across embedding and MCP execution paths, with concurrency and regression risks. The right issue is primarily a localized identifier-mapping and persistence correction with narrower compatibility concerns.
}
https://github.com/berriai/litellm/issues/32528 5:1 https://github.com/berriai/litellm/issues/28562

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

{
WaveSpeed requires a new provider spanning multiple API modalities, asynchronous workflows, authentication, model routing, and broad testing, while the telemetry issue is comparatively localized to span lifecycle ordering and regression coverage.
}
https://github.com/berriai/litellm/issues/34618 5:1 https://github.com/berriai/litellm/issues/33511

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

{
The left issue likely requires tracing and correcting budget enforcement across team, member, key, and request-accounting paths, with careful handling of limits, persistence, concurrency, and regression coverage. The right issue appears narrower: isolate a duplicated non-streaming instrumentation/callback path and apply a targeted guard or refactor, followed by focused tests.
}
https://github.com/berriai/litellm/issues/19105 3:1 https://github.com/berriai/litellm/issues/31121

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

{
The right-hand issue has substantially greater scope and risk: it requires cross-cutting proxy configuration, identity handling, isolation guarantees, and compatibility across multiple storage integrations. The left-hand issue is a localized provider request-path defect with a comparatively small fix and test surface.
}
https://github.com/berriai/litellm/issues/35109 10:1 https://github.com/berriai/litellm/issues/27434