docs(CLAUDE.md): refresh LLM provider routing notes for new src/llm/ architecture#6
Merged
offendingcommit merged 1 commit intomainfrom May 4, 2026
Merged
Conversation
…architecture The April-16 gotchas section was stale after the upstream sync (PR #4): - Legacy 'cf' / 'custom' provider tags removed — replaced by ModelTransport literal (anthropic/openai/gemini) and per-component MODEL_CONFIG__* env vars - 'deriver/summary must stay on cf' rule no longer applies — native gemini backend (src/llm/backends/gemini.py) honors response_format=json_schema - thoughtSignature multi-iteration workaround obsolete — preserved natively in src/llm/history_adapters.py + src/llm/executor.py - LM Studio section: env var names switched from LLM_OPENAI_COMPATIBLE_* globals to MODEL_CONFIG__OVERRIDES__BASE_URL / __API_KEY per component Adds a note that CF Gateway integration is now app-level (cf-aig-authorization auto-injected by src/llm/registry.py and src/embedding_client.py based on base_url pattern matching) rather than deployment-level URL routing. Ollama Cloud structured-output limitation kept — that's still a real upstream constraint, just rephrased for the new transport model.
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
1 participant
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.
The April-16 gotchas section in
CLAUDE.mdwas stale after the upstream sync (#4 + #5):cf/customprovider tags removed — replaced byModelTransportliteral (anthropic/openai/gemini) and per-component<COMPONENT>_MODEL_CONFIG__*env varscf" rule no longer applies — nativeGeminiBackend(src/llm/backends/gemini.py) honorsresponse_format=json_schemathoughtSignaturemulti-iteration workaround obsolete — preserved natively insrc/llm/history_adapters.py:77-78+src/llm/executor.py:43-44LLM_OPENAI_COMPATIBLE_*globals toMODEL_CONFIG__OVERRIDES__BASE_URL/__API_KEYper componentAdds a note that CF Gateway integration is now app-level (
cf-aig-authorizationauto-injected bysrc/llm/registry.pyandsrc/embedding_client.pybased onbase_urlpattern matching) rather than deployment-level URL routing.Ollama Cloud structured-output limitation kept — that's still a real upstream constraint, just rephrased for the new transport model.
Test plan
src/llm/registry.py,src/llm/backends/gemini.py,src/llm/history_adapters.py,src/llm/executor.py,src/llm/backends/openai.py)