MiniMax Cloud
Track the MiniMax Cloud connector approval boundary without claiming an unavailable managed integration.
For your agent
Read https://mem.nowledge.co/SKILL.md and this guide. Install the local MiniMax Marketplace package only in MiniMax Code. Treat MiniMax Cloud as unavailable until MiniMax confirms the managed App provider and scopes. Never paste a Mem key into chat or claim automatic transcript capture.
What this is
The Nowledge Mem MiniMax Marketplace package is mechanically ready for local MiniMax Code. MiniMax Cloud is a separate managed App/Connector surface. Its provider identifier and authorization scopes still require confirmation from MiniMax, so there is no supported Cloud connection to turn on yet.
Current status
- MiniMax Code: use the marketplace package and its credential-free local MCP connection.
- MiniMax Cloud: unavailable while the provider/App contract is pending MiniMax confirmation.
- Submission package: prepared without an invented App identifier, embedded Cloud credential, or claim of transcript capture.
When MiniMax confirms the managed provider, the catalog entry will name that exact provider and approved scopes, and the package will be versioned and validated again before Cloud is documented as available.
Capture and identity
Remote MCP gives MiniMax access to Mem; it does not give Mem a transcript hook. There is no automatic full-thread capture claim for this path. Use a supported export for historical conversations, or install a dedicated local connector when the local runtime provides hooks.
If several MiniMax agents share a workspace, configure each durable role with
an explicit AI Identity. source_app records provenance and must not be used
to infer an identity or create a Space.
Troubleshooting
- You see no Cloud Connect action: that is expected while provider approval is pending; do not substitute a raw API key.
- You use MiniMax Code locally: follow the marketplace package instructions and keep Nowledge Mem running on the same computer.
- A page claims MiniMax Cloud already works: report it as stale copy; the provider confirmation is the release gate.
