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

{
The left requires coordinated lifecycle handling across persistence synchronization, in-memory registries, updates, deletions, restarts, and multiple model-discovery paths, with broader regression and concurrency risk. The right is more likely an isolated provider-response parsing or non-streaming compatibility fix with narrower testing scope.
}
https://github.com/berriai/litellm/issues/33168 4:1 https://github.com/berriai/litellm/issues/26309