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

{
Issue 32245 is harder because it likely spans budget ownership, team/key association semantics, persistence, and scheduled reset logic, with greater risk of affecting accounting and existing authorization flows. Issue 25128 is comparatively localized to protocol-state handling in the outbound MCP client and can be addressed through request-session propagation and focused integration tests.
}
https://github.com/berriai/litellm/issues/32245 3:2 https://github.com/berriai/litellm/issues/25128