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

{
The left task is a broad, high-risk systems migration spanning architecture, language boundaries, performance targets, compatibility, and many subsystems. The right task is comparatively localized to one provider integration and request-translation path, with narrower testing and deployment impact.
}
https://github.com/berriai/litellm/issues/31263 20:1 https://github.com/berriai/litellm/issues/32456

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

{
The right issue is harder because it crosses framework integration, routing, provider detection, and conditional Responses-API translation, requiring careful regression coverage across multiple invocation paths. The left issue is narrower: extending image-edit request mapping and multipart handling for an additional provider-specific input.
}
https://github.com/berriai/litellm/issues/26897 3:2 https://github.com/berriai/litellm/issues/32456

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

{
The right issue is harder because it requires diagnosing distributed accounting, timeout and retry behavior, concurrency, persistence consistency, and multi-pod regression coverage. The left issue is comparatively narrower, centered on parameter propagation and endpoint selection across an integration path.
}
https://github.com/berriai/litellm/issues/30460 3:1 https://github.com/berriai/litellm/issues/26897

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

{
The left issue requires diagnosing and correcting distributed state consistency under retries, timeouts, concurrency, and multi-pod failure modes, with safeguards against financial mis-enforcement and regression testing. The right issue is a bounded provider integration involving request translation, model metadata, pricing, and usage reporting, with comparatively clearer implementation boundaries.
}
https://github.com/berriai/litellm/issues/30460 3:1 https://github.com/berriai/litellm/issues/31568

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

{
Issue 30460 is harder because it requires diagnosing and correcting distributed state, concurrency, timeout, reconciliation, and budget-enforcement behavior across multiple storage layers, with substantial regression risk. Issue 31833 is a more bounded authentication feature spanning API and dashboard flows, validation, persistence, and security tests.
}
https://github.com/berriai/litellm/issues/30460 3:1 https://github.com/berriai/litellm/issues/31833

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

{
The left task is harder because it requires diagnosing and correcting distributed state corruption under failures, preserving idempotency and budget correctness across pods and storage layers, and validating behavior under concurrency and timeout scenarios. The right task is a more bounded input-normalization enhancement with provider-specific conversion and validation.
}
https://github.com/berriai/litellm/issues/30460 3:1 https://github.com/berriai/litellm/issues/30501

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

{
The OpenCode Go work spans a new provider integration, model and pricing discovery, multiple protocol translations, proxy registration, and broader compatibility testing. The Azure failure is narrower in surface area, though it requires tracing parameter propagation across the LangChain adapter, router, bridge, and Azure request construction.
}
https://github.com/berriai/litellm/issues/31568 3:2 https://github.com/berriai/litellm/issues/26897

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

{
The right issue is harder because it requires repository-wide architectural, ownership, and compatibility decisions across many components, while the left is a comparatively contained provider-integration and request-plumbing change.
}
https://github.com/berriai/litellm/issues/34241 5:1 https://github.com/berriai/litellm/issues/32456

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

{
The left issue is substantially harder: it entails a large-scale runtime and language migration across core functionality, with compatibility, performance, rollout, and regression risks. The right issue is broad but comparatively more bounded to auditing ownership boundaries, reorganizing code, and documenting or enforcing licensing distinctions.
}
https://github.com/berriai/litellm/issues/31263 6:1 https://github.com/berriai/litellm/issues/34241

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

{
34241 requires broad cross-cutting architectural changes, repository-wide dependency and packaging decisions, and careful compatibility and licensing validation. 30460 is a more localized production bug involving distributed state, failure handling, and regression testing.
}
https://github.com/berriai/litellm/issues/34241 4:1 https://github.com/berriai/litellm/issues/30460