feat: add Vivgrid provider support#1100
Conversation
yinwm
left a comment
There was a problem hiding this comment.
Review Summary
Thanks for adding Vivgrid provider support! The implementation follows the existing patterns well and has good test coverage. However, there are a few issues that need to be addressed before merging.
🔴 Must Fix
1. Copy-paste error in README.md (line 942)
| `vivgrid` | LLM (Cerebras direct) | [vivgrid.com](https://vivgrid.com) |The description says "Cerebras direct" but it should be "Vivgrid" or "OpenAI-compatible". This is clearly a copy-paste mistake.
2. Table formatting broken in README.md (lines 975-977)
| **神算云** | `shengsuanyun/` | `https://router.shengsuanyun.com/api/v1` | OpenAI | |
| **Vivgrid** | `vivgrid/` | `https://api.vivgrid.com/v1` | OpenAI | [Get Key](https://vivgrid.com) |- The 神算云 row is missing the
-link column (looks like it was accidentally removed) - The Vivgrid row has trailing whitespace after the link
🟡 Suggestions
1. Model inference logic could be more precise (factory.go line 306)
case (strings.Contains(lowerModel, "vivgrid") || strings.HasPrefix(model, "vivgrid/")) && cfg.Providers.Vivgrid.APIKey != "":Using strings.Contains(lowerModel, "vivgrid") might be too loose. A model named my-vivgrid-model would incorrectly match. Consider using only the prefix check:
case strings.HasPrefix(model, "vivgrid/") && cfg.Providers.Vivgrid.APIKey != "":2. Extra blank line in docs/migration/model-list-migration.md (line 105)
There's an extra blank line added. Consider removing it for cleaner documentation.
✅ What's Done Well
- Code structure follows existing provider patterns (consistent with Cerebras, DeepSeek, etc.)
- Good test coverage for migration, factory, and normalize model functions
- All necessary files updated (config, factory, provider, tests, docs)
Please fix the README issues and I'll be happy to approve this PR!
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. 🤖 Generated with Claude Code - If this code review was useful, please react with 👍. Otherwise, react with 👎. |
feat: add Vivgrid provider support
|
@zihan987 Adding Vivgrid as a provider and reusing the openai_compat infrastructure is the right call. Keeps things clean and consistent with how other compatible endpoints are integrated. We have a PicoClaw Dev Group on Discord where contributors hang out and collaborate. If you'd like to join, send an email to |
feat: add Vivgrid provider support
feat: add Vivgrid provider support
feat: add Vivgrid provider support
feat: add Vivgrid provider support
📝 Description
Adds Vivgrid as a new LLM provider using the OpenAI-compatible endpoint (https://api.vivgrid.com/v1). Vivgrid is an AI Agent and LLM infrastructure platform that helps developers build, deploy, and operate AI-powered applications with speed, reliability, and cost efficiency.
vivgrid-openclaw
Vivgrid exposes an OpenAI-compatible API, so this implementation reuses the existing openai_compat provider
infrastructure.
Files changed:
———
🗣️ Type of Change
———
☑️ Checklist
———