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

{
OpenCode Go spans provider registration, model discovery, external metadata synchronization, pricing, endpoint-shape detection, request translation, and usage attribution across proxy paths. Stable key IDs are a more contained schema/API and rotation-flow change, though they require migration and backward compatibility.
}
https://github.com/berriai/litellm/issues/31568 3:1 https://github.com/berriai/litellm/issues/31310

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

{
The cache-consistency fix is harder because it requires diagnosing and safely coordinating cross-process state invalidation, Redis Pub/Sub delivery, worker lifecycle, race conditions, and multi-worker testing. The provider addition is broader than a simple adapter but can mostly follow established provider, metadata, and pricing integration patterns.
}
https://github.com/berriai/litellm/issues/27852 3:2 https://github.com/berriai/litellm/issues/31568

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

{
A new provider requires broader integration across model discovery, endpoint translation, pricing, usage accounting, configuration, and compatibility testing. The other task is comparatively localized to preserving an existing alias through one streaming observability path, with a narrower regression surface.
}
https://github.com/berriai/litellm/issues/31568 4:1 https://github.com/berriai/litellm/issues/25628

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

{
OpenCode Go requires a new provider integration spanning routing, model discovery, endpoint compatibility, pricing metadata, usage attribution, proxy behavior, and broad test coverage. The RAGFlow item is more likely a focused compatibility or response-parsing fix within an existing integration, with narrower scope and lower regression risk. Overall effort is estimated at roughly 3:1.
}
https://github.com/berriai/litellm/issues/31568 3:1 https://github.com/berriai/litellm/issues/28773

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

{
Issue #30043 is harder because it spans cross-provider protocol compatibility, streaming semantics, token accounting, routing behavior, and broad regression coverage, while #13786 is primarily a localized streaming termination and callback-control defect.
}
https://github.com/berriai/litellm/issues/30043 5:1 https://github.com/berriai/litellm/issues/13786

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

{
29320 is harder because it introduces a new cross-cutting feature with model/dependency management, multiple configuration scopes, callback integration, fail-open behavior, metadata and billing observability, and broad SDK/proxy test coverage. 30043 is risky protocol-compatibility work, but is comparatively narrower and centered on stabilizing existing routing, streaming, and token-counting paths.
}
https://github.com/berriai/litellm/issues/29320 5:3 https://github.com/berriai/litellm/issues/30043

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

{
Issue 30043 is harder because it requires cross-cutting protocol compatibility work, streaming correctness, provider-specific behavior, token accounting, and extensive regression testing across complex agent workflows. Issue 31824 is primarily scoped to authorization, usage aggregation, API design, and UI exposure.
}
https://github.com/berriai/litellm/issues/30043 3:1 https://github.com/berriai/litellm/issues/31824

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

{
Cross-provider protocol compatibility requires coordinated changes across request translation, streaming state, token accounting, regression coverage, and production validation, while the other item is primarily a CLI orchestration and configuration feature with bounded integration work.
}
https://github.com/berriai/litellm/issues/30043 4:1 https://github.com/berriai/litellm/issues/30421

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

{
Issue 21347 is harder because it requires designing and integrating a broad, specification-driven validation framework across many schemas, providers, response paths, and ongoing tests. Issue 30043 is substantial but comparatively bounded to stabilizing specific routing and compatibility behaviors.
}
https://github.com/berriai/litellm/issues/21347 5:3 https://github.com/berriai/litellm/issues/30043

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

{
30460 requires diagnosing and safely correcting distributed Redis/DB accounting under concurrency, transaction buffering, failures, and multi-pod deployment conditions, with substantial regression and data-integrity risk. 25191 is more localized to endpoint-specific tool-call interception and shared agent-loop behavior, with a narrower implementation and test surface.
}
https://github.com/berriai/litellm/issues/30460 4:1 https://github.com/berriai/litellm/issues/25191