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

{
The recursive-schema failure requires redesigning bounded expansion semantics across multiple provider translation paths, with careful handling of cycles, fan-out, memory/CPU limits, compatibility, and regression testing. The budget issue is narrower: it mainly needs atomic/concurrency-safe counter-window updates and reliable async write coordination in one accounting path.
}
https://github.com/berriai/litellm/issues/34328 3:1 https://github.com/berriai/litellm/issues/34733