Refactor model clients to use config-provided API key #43
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.
This PR refactors how API keys are managed across the model clients. Previously,
openai_client.pyandanthropic_client.pydirectly read from environment variables (e.g.,OPENAI_API_KEY,ANTHROPIC_API_KEY). This caused conflicts when using OpenAI’s official models as LLM-as-Judge while also switching to non-OpenAI but OpenAI-API-compatible model providers.Key changes include:
api_keypassed via configuration.api_keyto default configuration: A placeholder ("") ensures the field exists in all configs.api_keyis now read from configuration usingcfg.llm.get("api_key").This ensures a clean separation of concerns: