feat: add MiniMax provider support

[octo-patch]

Summary

• Add MiniMax as a selectable AI provider using the OpenAI-compatible API interface
• Register 'minimax' in the provider enum in src/db/tables.ts
• Add createModel case for MiniMax in src/ai/fetch.ts with base URL https://api.minimax.io/v1
• Add MiniMax to the provider dropdown in the new model form (src/settings/models/new.tsx)
• Add MiniMax to the provider enum in the model detail edit form (src/settings/models/detail.tsx)

Usage

1. Go to Settings → Models → Add Model
2. Select MiniMax as the provider
3. Enter model name: MiniMax-M2.7 or MiniMax-M2.7-highspeed
4. Enter your MiniMax API key (from https://platform.minimax.io)
5. Click Add Model

Supported Models

Model	Description
MiniMax-M2.7	Peak Performance. Ultimate Value. Master the Complex
MiniMax-M2.7-highspeed	Same performance, faster and more agile

API Reference

• Chat (OpenAI Compatible): https://platform.minimax.io/docs/api-reference/text-openai-api

Test plan

• Unit tests for form schema validation (MiniMax requires API key, does not require URL)
• Full test suite passes (2036 pass, 1 pre-existing skip unrelated to this PR)
• TypeScript type check passes (only pre-existing error in encryption.test.ts unrelated to this PR)

---

Note

Medium Risk
Introduces a new external LLM provider path and persists a new provider enum value, which could break model creation/selection or cause runtime errors if misconfigured. Changes are localized and reuse the existing OpenAI-compatible integration pattern.

Overview
Adds MiniMax as a first-class model provider across the stack: the models DB provider enum now includes minimax, the Settings → Models UI allows selecting it (new + detail forms), and the backend model factory (createModel) can instantiate it via createOpenAICompatible targeting https://api.minimax.io/v1 (API key required).

Also adds a focused Bun test (src/ai/fetch.test.ts) covering form-schema validation expectations for MiniMax (requires API key, does not require URL).

^{Reviewed by Cursor Bugbot for commit da72a19. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Reviewed by Cursor Bugbot for commit da72a19. Configure here.}

[cursor]

MiniMax UI added to unreachable component, not active page

High Severity

The MiniMax provider dropdown and schema changes are added to NewModelPage in new.tsx and ModelDetailPage in detail.tsx, but neither component is connected to any route. The only models page wired into the app router (src/app.tsx line 161) is ModelsPage from src/settings/models/index.tsx, which has its own form schema, provider dropdown, getProviderDisplay, and fetchAvailableModels — none of which include minimax. Users will be unable to select MiniMax as a provider through the UI.

Additional Locations (2)

• src/settings/models/new.tsx#L18-L19
• src/settings/models/detail.tsx#L30-L31

 

^{Reviewed by Cursor Bugbot for commit da72a19. Configure here.}

[cursor]

Tests validate duplicated schemas, not production code

Medium Severity

The test file defines local copies of the form schemas from new.tsx and detail.tsx rather than importing or testing the actual production code. These duplicated schemas will silently drift if the source schemas change, giving false confidence in test coverage. Additionally, the file is named fetch.test.ts but tests no function from src/ai/fetch.ts (like createModel).

 

^{Reviewed by Cursor Bugbot for commit da72a19. Configure here.}