feat(providers): add Augment, NVIDIA NIM, b.ai providers - #248
Conversation
Port three upstream providers into the KooshaPari fork: - Augment (Auggie CLI) local no-auth provider (port diegosouzapw#5972) - NVIDIA NIM image generation, FLUX models (port diegosouzapw#5971) - b.ai OpenAI-compatible API-key gateway (port diegosouzapw#5969) APIKEY_PROVIDERS grows 158 -> 159 (b.ai). Adds executor, image handler, registry entries, and unit tests (42 cases across auggie-executor, bai-provider, nvidia-nim-image). Co-authored-by: chamdanilukman <chamdanilukman@users.noreply.github.com> Co-authored-by: eng2007 <eng2007@users.noreply.github.com> Co-authored-by: DEYLNN <DEYLNN@users.noreply.github.com>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
Warning Review limit reached
Next review available in: 19 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (20)
Note
|
# Conflicts: # CHANGELOG.md
L17 Latency Budget ReportChecked against: budgets/rest-endpoints.yaml. |
L17 Latency Regression ReportThreshold: 10% p99 regression. |
|



Ports three high-value upstream providers into the fork, bundled.
Providers
open-sse/executors/auggie.ts+ registry entry.open-sse/handlers/imageGeneration/providers/nvidiaNim.ts+ imageRegistry wiring.https://api.b.ai/v1/models).Catalog impact
APIKEY_PROVIDERS: 158 → 159 (addsbai).bairegistered as a named OpenAI-style discovery provider and inPROVIDER_ENDPOINTS.Tests
42 unit cases, all green:
tests/unit/auggie-executor.test.ts(18)tests/unit/bai-provider.test.ts(8)tests/unit/nvidia-nim-image.test.ts(12)tests/unit/providers-constants-split.test.ts(4, count updated to 159)Qiniu/ModelScope references from the upstream diff were intentionally excluded — those belong to a separate bundle (task #27).