Skip to content

feat: add MiniMax provider support#28

Open
octo-patch wants to merge 1 commit into
HITsz-TMG:mainfrom
octo-patch:feature/add-minimax-provider
Open

feat: add MiniMax provider support#28
octo-patch wants to merge 1 commit into
HITsz-TMG:mainfrom
octo-patch:feature/add-minimax-provider

Conversation

@octo-patch

Copy link
Copy Markdown

Summary

Add MiniMax as a new LLM provider, compatible with the existing multi-provider architecture (OpenAI / Gemini / DeepSeek / DashScope). MiniMax uses an OpenAI-compatible Chat Completions API, so it slots in next to the existing DeepSeek / GPT clients.

Changes

  • Add MiniMax client backend/models/llm_minimax.py (OpenAI-compatible, base URL https://api.minimax.io/v1)
  • Register the minimax provider in backend/config.py and config.yaml.example
  • Route minimax-* model names to the MiniMax client in backend/models/llm_client.py
  • Register MiniMax-M3 (flagship) and MiniMax-M2.7 in the central model registry (backend/models/config_model.py), so they show up in the /api/models endpoint and the frontend selector
  • Surface the MiniMax provider in the frontend settings page and provider model groups
  • Document the provider in README.md / README_EN.md / SKILL.md
  • Add unit tests for provider config, model registry, and dispatcher routing

Why

MiniMax-M3 is the latest flagship model with a 1M context window, 128K max output, and image input, exposed through an OpenAI-compatible interface — a good fit for the script / storyboard LLM stages.

Testing

  • pytest backend/tests/ — 8 passed (provider config, model registry, routing)
  • Integration-verified the OpenAI-compatible endpoint and both model names (MiniMax-M3, MiniMax-M2.7) against https://api.minimax.io/v1

Add MiniMax as a new OpenAI-compatible LLM provider, alongside the
existing OpenAI / Gemini / DeepSeek / DashScope providers.

- Add MiniMax client (models/llm_minimax.py) on the OpenAI-compatible
  Chat Completions API (base_url https://api.minimax.io/v1)
- Register minimax provider config in backend config + config.yaml.example
- Route minimax-* models to the MiniMax client in llm_client.py
- Register MiniMax-M3 (flagship) and MiniMax-M2.7 in the model registry
- Expose MiniMax provider in the frontend settings page and model groups
- Document the provider in README / README_EN / SKILL.md
- Add unit tests for provider config, registry, and model routing
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