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

{
The left requires cross-cutting compatibility work across provider routing, streaming translation, structured content/tool handling, token accounting, and regression testing. The right appears comparatively localized to identifier encoding/decoding in one Responses API path, with narrower integration risk.
}
https://github.com/berriai/litellm/issues/30043 5:1 https://github.com/berriai/litellm/issues/25757