This reverts commit 366f9c18a, keeping the git-native knowledge base in
dev until the issues queued for the next release are fixed.
Nothing shipped by that merge was reachable in production: git-native
behaviour needs both the KNOWLEDGE_STORE_ENABLED env (default FALSE) and
a per-workspace column (default false), so reverting changes no runtime
behaviour.
Migrations 175 and 176 stay applied in production; alembic_version is
moved back to 174 by hand so this tree's upgrade is a no-op. Both
revisions only add columns, and they use ADD COLUMN IF NOT EXISTS, so
re-landing this work re-applies them harmlessly.
- Add MiniMax-M3 to the model selection list (set as the new default)
- Add MiniMax-M2.7 and MiniMax-M2.7-highspeed as alternatives
- Remove deprecated MiniMax-M2.5 / M2.5-highspeed entries
- Update example config and Chinese setup docs to reference M3 (512K context)
Add full MiniMax provider support across the entire stack:
Backend:
- Add MINIMAX to LiteLLMProvider enum in db.py
- Add MINIMAX mapping to all provider_map dicts in llm_service.py,
llm_router_service.py, and llm_config.py
- Add Alembic migration (rev 106) for PostgreSQL enum
- Add MiniMax M2.5 example in global_llm_config.example.yaml
Frontend:
- Add MiniMax to LLM_PROVIDERS enum with apiBase
- Add MiniMax-M2.5 and MiniMax-M2.5-highspeed to LLM_MODELS
- Add MINIMAX to Zod validation schema
- Add MiniMax SVG icon and wire up in provider-icons
Docs:
- Add MiniMax setup guide in chinese-llm-setup.md
MiniMax uses an OpenAI-compatible API (https://api.minimax.io/v1)
with models supporting up to 204K context window.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add support for DeepSeek, Qwen (Alibaba), Kimi (Moonshot), and GLM (Zhipu)
- Implement auto-fill API Base URL when selecting Chinese LLM providers
- Add smart validation and warnings for missing API endpoints
- Fix session state management in task logging service
- Add comprehensive Chinese setup documentation
- Add database migration for new LLM provider enums
Closes#383
