feat(agent-config): add 10 new LLM provider families to dropdown and config UI - #162
feat(agent-config): add 10 new LLM provider families to dropdown and config UI#162prasadadhav wants to merge 2 commits into
Conversation
|
Frontend wiring looks clean and the provider keys match the backend (#575) exactly. Same two gaps as the paired backend PR — flagging here for tracking, both were the bar on the Ollama PR: 1. No docs. The provider reference in 2. No tests. No coverage for the new providers on this side either. The Ollama PR added a round-trip test on the backend; over here a small test exercising Otherwise LGTM. |
|
Hi Armen :) |
b70a218 to
b875a25
Compare
…families Add Mistral, DeepSeek, Google (Gemini), Meta (Llama), Anthropic (Claude), Qwen, xAI (Grok), Groq, Together AI, and OpenRouter to all provider-key locations: AgentLLMProviderType union, AgentLLMProvider type, AgentConfigurationPanel dropdown options and normalization whitelist, isChatCompatibleProvider predicate, and AgentConfigYamlEditor form fields with YAML serializer stanzas and collapsible UI sections per provider.
…d VALID_AGENT_LLM_PROVIDERS module-level const (used internally by normalizeAgentRuntimeConfig) - AgentConfigurationPanel.tsx: added export to AGENT_LLM_PROVIDER_OPTIONS, normalizeAgentLLMElement, AgentLLMElementProvider, and AgentLLMElement - New agent-llm.test.ts: 48 parametrized cases covering all three things the reviewer asked for normalizeAgentLLMElement preserves new keys without falling back to openai, dropdown options completeness, and local-storage whitelist completeness. 48/48 pass. (The 1 pre-existing failure in modifiers.test.ts is unrelated to our changes.)
b875a25 to
41daf80
Compare
|
Nice perfect, when it's released in BAF I will release it here |
2 participants
Summary
AgentLLMProviderType(editor package) andAgentLLMProvider(webappshared types) union types with all 10 new provider keys.
AGENT_LLM_PROVIDER_OPTIONSinAgentConfigurationPanel(e.g. "Google (Gemini)", "xAI (Grok)", "Meta (Llama)").normalizeAgentLLMElementand the local-storage validation whitelist toaccept all new keys (array-based check, replaces hardcoded conditionals).
isChatCompatibleProviderinagent-state-update.tsxto returntrueforall new families (all support chat-completion).
<Section>components in
AgentConfigYamlEditorfor each new provider'sapi_key.'huggingfaceapi'(no underscore) alongside canonical'huggingface_api'to avoid breaking existing saved configs.Related PRs: