docs: clarify agent-side vs server-side fallback adapters in CLAUDE.md#1408
Merged
toubatbrian merged 1 commit intomainfrom May 7, 2026
Conversation
|
toubatbrian
approved these changes
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated CLAUDE.md to distinguish between agent-side FallbackAdapter classes (in llm/, stt/, tts/ for client-side failover) and server-side fallback support in the Inference module (LiveKit Inference Gateway). The previous documentation didn't make this distinction clear, potentially causing confusion about where failover happens.
Introduced by commit 0f4cd61 (@tmshapland).
Without this clarification, agents reading CLAUDE.md might incorrectly assume all fallback logic is in one location, or developers might not understand that there are two distinct failover mechanisms: one they instantiate directly (agent-side adapters) and one provided by the inference gateway (server-side).
Doc Drift PRs can be configured here.