Skip to content

fix: add Vivgrid provider#2799

Merged
amitksingh1490 merged 8 commits intotailcallhq:mainfrom
fanweixiao:feature/add-vivgrid-provider
Apr 24, 2026
Merged

fix: add Vivgrid provider#2799
amitksingh1490 merged 8 commits intotailcallhq:mainfrom
fanweixiao:feature/add-vivgrid-provider

Conversation

@fanweixiao
Copy link
Copy Markdown
Contributor

Summary

Add Vivgrid as a built-in LLM provider using the OpenAI Responses API, including Vivgrid-hosted GPT-5.4 and Codex model entries.

Context

Vivgrid documents Codex-style integrations using https://api.vivgrid.com/v1 with VIVGRID_KEY and the Responses wire API. This project already supports multiple built-in providers through provider registry metadata, so Vivgrid can be integrated by registering it as a built-in provider and routing it through the existing OpenAI Responses backend.

Changes

  • Added ProviderId::VIVGRID as a built-in provider
  • Added Vivgrid provider registry config with VIVGRID_KEY
  • Configured Vivgrid to use OpenAIResponses
  • Added Vivgrid model entries for gpt-5.4, gpt-5.2-codex, and gpt-5.1-codex
  • Extended provider tests to cover Vivgrid ID parsing, display name, built-in registration, and provider config loading

Key Implementation Details

Vivgrid is registered as a built-in provider in the domain layer so it participates in provider ordering, display-name rendering, and string parsing consistently with the other first-party providers. In the provider registry, Vivgrid is configured to hit https://api.vivgrid.com/v1/responses and use VIVGRID_KEY, matching Vivgrid’s published integration guidance. The provider is wired to the existing OpenAIResponses response type so no new repository implementation was required.

Use Cases

  • Configure Forge to use Vivgrid without relying on generic custom-provider setup
  • Run coding workflows against Vivgrid-hosted Codex models
  • Use Vivgrid-hosted GPT-5.4 as a built-in selectable model provider

Testing

cargo test -p forge_domain test_vivgrid_from_str

cargo test -p forge_repo provider_repo::tests::test_load_provider_configs is currently blocked in this environment because protoc is not installed.

Co-Authored-By: ForgeCode <noreply@forgecode.dev>
@github-actions github-actions Bot added the type: feature Brand new functionality, features, pages, workflows, endpoints, etc. label Apr 2, 2026
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Apr 2, 2026

CLA assistant check
All committers have signed the CLA.

@tusharmath
Copy link
Copy Markdown
Collaborator

We need a few test keys to verify if this works.

@fanweixiao
Copy link
Copy Markdown
Contributor Author

We need a few test keys to verify if this works.

No problem, you can register an account on vivgrid, and send your account to me (cc@vivgrid.com), I'll sponsor credits to you.

@github-actions
Copy link
Copy Markdown

Action required: PR inactive for 5 days.
Status update or closure in 10 days.

@github-actions github-actions Bot added the state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. label Apr 13, 2026
@fanweixiao
Copy link
Copy Markdown
Contributor Author

Hi @tusharmath, I've already tested. See if this PR can be merged?

@github-actions github-actions Bot removed the state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. label Apr 14, 2026
@tusharmath tusharmath added the type: provider Updates provider.json configuration. label Apr 17, 2026
@github-actions
Copy link
Copy Markdown

Action required: PR inactive for 5 days.
Status update or closure in 10 days.

@github-actions github-actions Bot added the state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. label Apr 22, 2026
@amitksingh1490
Copy link
Copy Markdown
Contributor

@fanweixiao can you please rebase this once

@amitksingh1490 amitksingh1490 removed the state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. label Apr 22, 2026
@amitksingh1490 amitksingh1490 changed the title feature: add Vivgrid provider fix: add Vivgrid provider Apr 24, 2026
@amitksingh1490 amitksingh1490 added type: fix Iterations on existing features or infrastructure. and removed type: feature Brand new functionality, features, pages, workflows, endpoints, etc. labels Apr 24, 2026
@amitksingh1490 amitksingh1490 merged commit 726ef1d into tailcallhq:main Apr 24, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: fix Iterations on existing features or infrastructure. type: provider Updates provider.json configuration.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants