Skip to content

feat(ai): add MiniMax provider - #128

Open
octo-patch wants to merge 1 commit into
team9ai:mainfrom
octo-patch:octo/20260729-provider-add-recvqaCKXk6F7D
Open

feat(ai): add MiniMax provider#128
octo-patch wants to merge 1 commit into
team9ai:mainfrom
octo-patch:octo/20260729-provider-add-recvqaCKXk6F7D

Conversation

@octo-patch

Copy link
Copy Markdown

Reason: The server AI client had no MiniMax provider or MiniMax-M3 / MiniMax-M2.7 model validation, so MiniMax could not be selected as a first-class provider.

Summary

  • add a first-class MiniMax adapter to the existing ai-client provider registry
  • reuse the OpenAI SDK for blocking and streaming chat completions through a configurable base URL (default https://api.minimax.io/v1)
  • register the MiniMax-M3 and MiniMax-M2.7 models and the new provider type across the AI client and the shared microservice contracts
  • support database configuration plus MINIMAX_API_KEY / MINIMAX_API_BASE environment variables (set the base URL to switch regional endpoints)

Testing

  • corepack pnpm --filter @team9/shared build
  • corepack pnpm --filter @team9/database build
  • corepack pnpm --filter @team9/ai-client build
  • corepack pnpm --filter @team9/database test config.service.spec.ts --runInBand (2 passed)
  • eslint on the changed server files
  • prettier --check on the changed TypeScript files
  • git diff --check

Notes

  • apps/server/.env.example only adds optional runtime configuration.
  • No README, documentation, logo, sponsor, credits, or partner changes.

Register a first-class MiniMax adapter in the ai-client provider
registry. MiniMax exposes an OpenAI-compatible chat completions API, so
the adapter reuses the OpenAI SDK for blocking and streaming requests
through a configurable base URL (default https://api.minimax.io/v1).

- add the MINIMAX provider enum, MiniMax-M3 / MiniMax-M2.7 model list,
  and provider/model validation wiring across ai-client and the shared
  microservice contracts
- wire MINIMAX_API_KEY and MINIMAX_API_BASE database/env configuration
- cover the new provider config resolution with a unit test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant