Skip to content

feat(openmemory-py): upgrade MiniMax default chat model to M3#184

Open
octo-patch wants to merge 1 commit into
CaviraOSS:mainfrom
octo-patch:feature/upgrade-minimax-m3
Open

feat(openmemory-py): upgrade MiniMax default chat model to M3#184
octo-patch wants to merge 1 commit into
CaviraOSS:mainfrom
octo-patch:feature/upgrade-minimax-m3

Conversation

@octo-patch
Copy link
Copy Markdown
Contributor

Summary

Upgrade the MiniMax adapter in openmemory-py to default to the new
flagship MiniMax-M3 model. MiniMax-M2.7 and MiniMax-M2.7-highspeed
remain available as explicit alternatives.

Changes

  • packages/openmemory-py/src/openmemory/ai/minimax.py: change the fallback
    default chat model from MiniMax-M2.7 to MiniMax-M3 (still overridable
    via the model= argument or OM_MINIMAX_MODEL env var).
  • packages/openmemory-py/tests/test_minimax.py:
    • Update the default-model assertion to expect MiniMax-M3.
    • Switch the custom-model unit test and the integration smoke test to use
      MiniMax-M2.7-highspeed, the still-supported low-latency variant.
  • packages/openmemory-py/README.md: refresh the minimax section to list
    MiniMax-M3 (default), MiniMax-M2.7, and MiniMax-M2.7-highspeed.

Why

MiniMax-M3 is the current flagship chat model. Pointing the default at it
means new users get the latest capabilities (longer context, better quality)
out of the box, while users who pin a specific model can still pick the
M2.7 variants.

Testing

  • pytest tests/test_minimax.py -k "not Integration" — all 24 unit tests
    pass.
  • Spot-checked both MiniMax-M3 (default) and MiniMax-M2.7-highspeed
    against https://api.minimax.io/v1 — both are accepted by the API.

No changes to embeddings, base URL, env vars, or temperature handling.

Upgrade the MiniMax adapter default chat model from MiniMax-M2.7 to the new
MiniMax-M3 flagship. M2.7 and M2.7-highspeed remain available as explicit
alternatives via the `model=` argument or `OM_MINIMAX_MODEL` env.

- src/openmemory/ai/minimax.py: change fallback default to "MiniMax-M3"
- tests/test_minimax.py: update default-model assertion and switch the custom
  / integration test models to MiniMax-M2.7-highspeed (the still-supported
  fast variant)
- README.md: update the chat-model availability note for the minimax section
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