feat: add EvoLink OpenAI-compatible provider - #45
Open
EvoLinkAI wants to merge 1 commit into
Open
Conversation
Author
|
Validation evidence from local macOS run: Live EvoLink call through the provider selection path: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TLDR
Adds EvoLink as a first-class OpenAI-compatible provider for the main OpenGame agent LLM. EvoLink uses the existing OpenAI-compatible flow with
OPENAI_BASE_URL=https://direct.evolink.ai/v1, so the provider inherits the default request/client behavior and only needs provider detection, registration, tests, and configuration docs.Dive Deeper
EvoLinkOpenAICompatibleProvider, selected when the configured base URL containsdirect.evolink.ai..env.example.Reviewer Test Plan
Use an EvoLink API key with the OpenAI-compatible auth flow:
The provider factory should select
EvoLinkOpenAICompatibleProvider, while requests continue through the standard OpenAI-compatible chat completions path.Testing Matrix
Validated locally on macOS with Node v24.13.1:
npm run test --workspace=packages/core -- src/core/openaiContentGenerator/provider src/core/openaiContentGenerator/index.test.ts— 7 test files / 75 tests passed.npx eslint packages/core/src/core/openaiContentGenerator/index.ts packages/core/src/core/openaiContentGenerator/index.test.ts packages/core/src/core/openaiContentGenerator/provider/index.ts packages/core/src/core/openaiContentGenerator/provider/evolink.ts packages/core/src/core/openaiContentGenerator/provider/evolink.test.ts --max-warnings 0— passed.npm run typecheck --workspace=packages/core— passed.npm run build --workspace=packages/core— passed.gpt-5.2returnedprovider=EvoLinkOpenAICompatibleProvider,model=gpt-5.2-2025-12-11,content=OK.Linked issues / bugs
Resolves #44