8 views
-/https://github.com/berriai/litellm/issues/30484
GitHub · issue

#30484 LiteLLM Stability Sprint Roadmap

  • State: open
  • Author: @ishaan-berri
  • Labels: enhancement, proxy

Hi all, we are treating stability as a first class citizen. Sharing our roadmap for bug fixes and stability improvements planned over this week. Please comment what bugs you'd like to see fixed over this sprint

## AI Engineering - LLM Translation

- [x] `/v1/model/info` returns inconsistent responses for team-based models, so team-scoped model metadata needs to be reconciled. - [ ] Container/code-interpreter file retrieval on Azure fails for service-account virtual keys (403 / "no persisted bytes available"), so file content fetches need to work end-to-end under scoped non-admin keys. (LIT-3769) - [ ] Streaming file uploads fail with agents SDK in v1.88.0 on /v1/responses API (LIT-3737) - [x] Bedrock Mantle not working for OpenAI (Urgent Bug/Blocker)

## Spend Tracking and Budgets

- [ ] P0: Virtual key spend limits are not being enforced (LIT-3772) - [x] P0: Anthropic cost tracking is inaccurate for cached and tiered usage (LIT-3771)

## UI + Auth

- [ ] Budget reset timing isn't recalculated correctly when the duration changes. (LIT-3362) - [x] Add verification_uri_complete to CLI SSO device flow (LIT-3693) (Urgent Blocking Bug/Regression)

## Performance

- [x] Guardrails con…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (4 events)
#0 of 0 · 31d18h54m9s ago — entered · #import:https:::github.com:berriai:litellm post #1979
#30484 spans multiple subsystems, priorities, and regression-sensitive workstreams, requiring broad coordination and validation; #27835 is a narrower provider-integration change with limited scope.
#30484 is harder because it is a broad, cross-cutting initiative spanning multiple subsystems and requiring coordinated validation, whereas #20867 is a relatively localized error-handling and logging fix.
The right issue is substantially harder because it spans multiple cross-cutting subsystems, regressions, authorization paths, accounting, and performance work, whereas the left issue is a focused provider-specific endpoint integration.
#0 of 0 · 31d17h50m35s ago — current · #import:https:::github.com:berriai:litellm post #3038
The roadmap issue spans multiple subsystems and unrelated stability work, requiring broader coordination, prioritization, and validation. The router issue is narrower, involving per-deployment policy plumbing plus synchronized cache-expiration behavior.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search