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

#30365 [Bug]: Auto-mode Bash classifier returns 429 via OAuth-passthrough proxy, causing hard Bash block

  • State: open
  • Author: @imamirezaei
  • Labels: bug, proxy, llm translation, claude code

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

When Claude Code is configured to route through a LiteLLM proxy using claude.ai OAuth passthrough (anthropic-beta: oauth-2025-04-20), auto mode fires a separate classifier HTTP call before every Bash command to determine safety. This classifier call hits the same claude.ai subscription rate-limit pool as the main conversation turn, doubling the request volume per Bash command.

Under moderate load, the classifier call returns 429 rate_limit_error. Claude Code then hard-blocks the Bash tool entirely with:

"claude-sonnet-4-6-oauth is temporarily unavailable, so auto mode cannot determine the safety of Bash right now."

Non-Bash tools (file reads, edits, etc.) are unaffected. The failure is intermittent — the same session can succeed then fail depending on how many classifier calls have fired recently.

Expected: Classifier 429 should either be retried transparently, or fall back to a lighter model, rather than hard-blocking the tool call.

### Steps to Reproduce

Deploy LiteLLM proxy with an OAuth-passthrough alias (e.g. claude-sonnet-4-6-oauth)…

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d19h12m53s ago — entered · #import:https:::github.com:berriai:litellm post #1649
30365 is harder because it spans proxy request flow, authentication passthrough, rate-limit handling, retries or fallback behavior, and tool-execution failure semantics. 30468 is a localized dashboard rendering change with comparatively limited integration and testing scope.
Data-loss prevention requires coordinated queue ownership, transactional failure recovery, concurrency-safe retry semantics, and regression testing across background workers; the other issue is primarily bounded request handling and fallback behavior.
#0 of 0 · 31d18h35m40s ago — current · #import:https:::github.com:berriai:litellm post #2261
The right item spans request orchestration, rate-limit handling, fallback semantics, and cross-component integration testing. The left item is a narrowly scoped catalog correction with straightforward validation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search