Problem or Motivation
OpenMAIC’s built-in model/provider registry can lag behind fast-moving model releases. Recent models such as GPT Image 2, Claude Opus 4.7, Qwen3.6, DeepSeek V4, Kimi K2.6, Tencent HY3, Xiaomi MiMo v2.5, and newer Grok variants should be easier to select in the UI and configure from server-side env/YAML.
There is also an extensibility gap: when server config provides *_MODELS with a model ID that is not already in the local registry, the current sync path can drop that model. This makes newly released models difficult to use before the app registry is updated.
Proposed Solution
Refresh the built-in provider/model lists:
- OpenAI: add
gpt-5.4-pro; add an OpenAI image provider for gpt-image-2, gpt-image-2-2026-04-21, gpt-image-1.5, gpt-image-1, gpt-image-1-mini, and chatgpt-image-latest.
- Anthropic: add
claude-opus-4-7.
- Qwen: add
qwen3.6-max-preview, qwen3.6-plus, qwen3.6-plus-2026-04-02, qwen3.6-flash, qwen3.6-flash-2026-04-16, and qwen3.6-35b-a3b.
- Qwen Image: add
qwen-image-2.0-pro, qwen-image-2.0-pro-2026-03-03, qwen-image-2.0, and qwen-image-2.0-2026-03-03.
- DeepSeek: add
deepseek-v4-pro, deepseek-v4-pro[1m], and deepseek-v4-flash.
- Kimi: add
kimi-k2.6.
- xAI/Grok: add canonical
grok-4.20-reasoning, grok-4.20, and grok-4.20-multi-agent, while keeping existing beta IDs for compatibility.
- Tencent/Hunyuan: add a provider-level integration using prefixes such as
TENCENT and TENCENT_HUNYUAN. Do not add HY3 as an env prefix because HY3 is a model name, not a provider name.
- Xiaomi: add a Xiaomi MiMo provider with
mimo-v2.5-pro and mimo-v2.5.
Improve server-config extensibility:
- Preserve unknown server-provided model IDs from
*_MODELS as synthetic { id, name } entries instead of filtering them out.
- Keep aggregator-specific IDs out of default direct-provider lists unless they are official direct API IDs.
- Allow those IDs through
*_MODELS or custom providers.
Update settings UI, i18n, .env.example, README docs, and targeted tests.
Related Issues / Routing
Alternatives Considered
- Only document custom provider setup for new models. This avoids registry updates but makes common recent models harder to discover.
- Add all observed aggregator IDs directly to built-in providers. This is convenient but risks mixing official direct API IDs with OpenRouter or third-party routing IDs.
- Add a generic live model catalog fetch feature. This would be broader but is more complex than the immediate registry/config refresh.
Area
API / Backend
Additional Context
References:
Problem or Motivation
OpenMAIC’s built-in model/provider registry can lag behind fast-moving model releases. Recent models such as GPT Image 2, Claude Opus 4.7, Qwen3.6, DeepSeek V4, Kimi K2.6, Tencent HY3, Xiaomi MiMo v2.5, and newer Grok variants should be easier to select in the UI and configure from server-side env/YAML.
There is also an extensibility gap: when server config provides
*_MODELSwith a model ID that is not already in the local registry, the current sync path can drop that model. This makes newly released models difficult to use before the app registry is updated.Proposed Solution
Refresh the built-in provider/model lists:
gpt-5.4-pro; add an OpenAI image provider forgpt-image-2,gpt-image-2-2026-04-21,gpt-image-1.5,gpt-image-1,gpt-image-1-mini, andchatgpt-image-latest.claude-opus-4-7.qwen3.6-max-preview,qwen3.6-plus,qwen3.6-plus-2026-04-02,qwen3.6-flash,qwen3.6-flash-2026-04-16, andqwen3.6-35b-a3b.qwen-image-2.0-pro,qwen-image-2.0-pro-2026-03-03,qwen-image-2.0, andqwen-image-2.0-2026-03-03.deepseek-v4-pro,deepseek-v4-pro[1m], anddeepseek-v4-flash.kimi-k2.6.grok-4.20-reasoning,grok-4.20, andgrok-4.20-multi-agent, while keeping existing beta IDs for compatibility.TENCENTandTENCENT_HUNYUAN. Do not addHY3as an env prefix because HY3 is a model name, not a provider name.mimo-v2.5-proandmimo-v2.5.Improve server-config extensibility:
*_MODELSas synthetic{ id, name }entries instead of filtering them out.*_MODELSor custom providers.Update settings UI, i18n,
.env.example, README docs, and targeted tests.Related Issues / Routing
Alternatives Considered
Area
API / Backend
Additional Context
References: