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

{
#34733 requires coordinated changes to concurrent distributed accounting, atomic state transitions, asynchronous write guarantees, and race-focused testing; #23348 is a set of mostly localized MCP validation and lookup fixes.
}
https://github.com/berriai/litellm/issues/34733 3:1 https://github.com/berriai/litellm/issues/23348

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

{
Issue 23841 spans multiple translation paths, content formats, provider routing modes, and integration regressions, creating broader implementation and testing risk. Issue 25947 appears more localized to proxy configuration loading and vector-store initialization.
}
https://github.com/berriai/litellm/issues/23841 3:1 https://github.com/berriai/litellm/issues/25947

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

{
The concurrency fix is harder because it requires a race-free, distributed accounting design with atomic admission, failure handling, compatibility guarantees, and stress testing. The UI work is broader across configuration sources and security boundaries but is comparatively conventional read-only API and frontend integration.
}
https://github.com/berriai/litellm/issues/34732 5:4 https://github.com/berriai/litellm/issues/30641

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

{
34732 requires cross-request coordination and careful atomicity, rollback, and concurrency testing across deployment boundaries; 23841 is broader but mainly localized adapter fixes with targeted regression coverage.
}
https://github.com/berriai/litellm/issues/34732 5:3 https://github.com/berriai/litellm/issues/23841

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

{
Nested access-group composition is harder because it changes authorization data modeling and resolution semantics, requiring recursive expansion, cycle protection, propagation/invalidation behavior, compatibility handling, and broad API, persistence, and test coverage. The budget fix is risky due to distributed concurrency and atomic accounting, but is more narrowly scoped to admission and storage coordination.
}
https://github.com/berriai/litellm/issues/28032 3:2 https://github.com/berriai/litellm/issues/34732

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

{
The right issue is harder because it requires designing and validating atomic distributed admission control, reservation semantics, failure handling, and compatibility with concurrent multi-replica traffic. The left issue is a more bounded standards-compliance change involving request handling, metadata exposure, configuration, and tests.
}
https://github.com/berriai/litellm/issues/34732 5:3 https://github.com/berriai/litellm/issues/31296

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

{
The concurrency fix is harder because it requires designing atomic distributed admission control, handling reservation and failure semantics, and validating race conditions across replicas. The other issue is broad but primarily structured test coverage and CI validation over an existing implementation.
}
https://github.com/berriai/litellm/issues/34732 3:2 https://github.com/berriai/litellm/issues/26535

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

{
34733 is harder because it requires coordinating concurrent window transitions, preserving consistency across related distributed state, and making asynchronous accounting reliable; 34732 has a narrower admission-control synchronization problem.
}
https://github.com/berriai/litellm/issues/34733 5:4 https://github.com/berriai/litellm/issues/34732

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

{
The right issue is harder because it requires redesigning data retrieval and session reconstruction for bounded memory while preserving ordering and conversation correctness across large histories, with database-level performance validation. The left issue is more localized to adapting guardrail response inspection for an alternate response representation and adding focused enforcement tests.
}
https://github.com/berriai/litellm/issues/33666 3:1 https://github.com/berriai/litellm/issues/32201

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

{
#33371 requires a new cross-cutting public contract, provider-specific normalization, router integration, compatibility decisions, and broader testing. #33666 is comparatively localized to query shape, bounded retrieval, and session-reconstruction correctness.
}
https://github.com/berriai/litellm/issues/33371 3:1 https://github.com/berriai/litellm/issues/33666