feat: Add Claude Agent SDK as a provider - #330
Conversation
…iguration file, and fixed a false error in evaluator.
|
Thanks for this — the no-API-key angle (running on an existing Claude Code / SDK login) is a neat idea. We're standardizing on the config-driven provider layer from #298: Claude API access now lands via a |
Add an `anthropic` provider block to providers.json using Anthropic's OpenAI-compatible endpoint (https://api.anthropic.com/v1). No new code is needed — the config-driven OpenAICompatibleProvider (from interviewstreet#298) handles it, the same way Gemini is wired via its OpenAI-compatible endpoint. Registers claude-opus-4-8, claude-sonnet-5, and claude-haiku-4-5, keyed on ANTHROPIC_API_KEY. structured_output is set to json_object (Anthropic's OpenAI-compatible layer has limited json_schema support; the pipeline also cleans up JSON via extract_json_from_response). Supersedes the pre-interviewstreet#298 Claude-provider PRs that added bespoke provider classes: interviewstreet#205, interviewstreet#224, interviewstreet#235, interviewstreet#279, interviewstreet#303, interviewstreet#330, interviewstreet#348. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Thanks for letting me know! If you ever decide to allow this functionality (makes Claude code users lives much easier), I've updated my fork to work with the main repository's new system in this PR. Thank you for all you do! |
2 participants
This adds Claude Agent SDK as a provider.