Repository navigation
v0.9.0
What's Changed
Chat backend: OpenAI and Anthropic API keys
reviewer.chat.provider lets the chat backend call the OpenAI or Anthropic API directly with their own keys:
reviewer.chat.provider |
Endpoint | Key when reviewer.chat.apiKey is unset |
|---|---|---|
"openai-compatible" (default, unchanged) |
<baseURL>/chat/completions |
AUTO_APPROVAL_CHAT_API_KEY |
"openai" |
https://api.openai.com/v1/chat/completions |
OPENAI_API_KEY |
"anthropic" |
https://api.anthropic.com/v1/messages (Messages API) |
ANTHROPIC_API_KEY |
- The vendor providers always call the vendor's own host and take no
baseURL, so their key never reaches another server. - The Anthropic provider uses the native Messages API (
x-api-key,anthropic-version: 2023-06-01,max_tokens: 16000). Only a finished reply (end_turn/stop_sequence) is read for a verdict; a refusal or any other early stop fails the review, and "prompt is too long" or running out of context window counts as too large. - Works for the decision backend's
onOversize: "chat"fallback too.
- feat: call the OpenAI and Anthropic APIs from the chat backend by @dyoshikawa in #56
Contributors
Full Changelog: v0.8.0...v0.9.0