No Minimax-M3 in Mammouth Code#33015
Conversation
I feel embarrassed for taking so long to spot this. I ran around and around in circles, looking far into the horizon and the sky for answers, when the solution was right under my feet, at the start of the journey. Playing Disco Elysium yesterday made me a poet today :D
Upgrade opencode to v1.1.51
chore: merge upstream v1.4.0 into dev
- Export MAMMOUTH_PROVIDER and wire fetchMammouthModels() into get() so the mammouth-ai provider is always present with live models - Add mammouth-ai entry in the custom() handlers alongside opencode: reads key from MAMMOUTH_API_KEY env var or auth store; strips paid models when no key is found; autoloads when a key is present
When running `mammouth providers login`, users were shown a full list of all providers from models.dev (Anthropic, OpenAI, MiniMax, etc.) which is confusing since Mammouth uses its own models. Now the login command skips the picker entirely and directly asks for the Mammouth API key, storing it under the mammouth-ai provider id.
Installation.latest() was fetching versions from upstream opencode release channels (github.com/anomalyco/opencode, npmjs.org, brew...) causing misleading "opencode X.Y.Z available" messages for Mammouth users. Return early so no update check runs until Mammouth has its own channel.
The per-directory config scan only loaded opencode.json/opencode.jsonc. Users with a .opencode/mammouth.jsonc (e.g. custom provider or model config) were silently ignored after each upstream merge. Note: the global ~/.config/mammouth/mammouth.jsonc is already loaded correctly by loadGlobal() — this only affects project-level dirs.
Fix/config issue
fixing locale wip
github-actions
Bot
added
the
needs:compliance
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
Hey! Your PR title Please update it to start with one of:
Where See CONTRIBUTING.md for details. |
|
The following comment was made by an LLM, it may be inaccurate: Based on my search, I found one potentially related PR: Related PR:
This PR is related to MiniMax provider handling, which could be relevant to your PR about Minimax-M3 in Mammouth Code. However, it appears to address tool results rather than model availability. The other results are about different providers (GLM, thinking parts) and not directly related to your Minimax-M3 issue. |
4 participants
https://app.notion.com/p/mammouth/No-Minimax-M3-in-Mammouth-Code-381cf297c1ca81eba128f6c54d9c9859