cyberine
UsageRun recipes

MiniMax mmx — text worker + image/speech tools

The MiniMax mmx CLI is two capabilities in Cyberine: a TEXT worker (mmx-text-build) and two multimedia IMPLEMENTER tools (mmximagegenerate, mmxspeechsynthesize). Auth is flexible — EITHER export...

The MiniMax mmx CLI is two capabilities in Cyberine: a TEXT worker (mmx-text-build) and two multimedia IMPLEMENTER tools (mmx_image_generate, mmx_speech_synthesize). Auth is flexible — EITHER export MMX_TOKEN_KEY, OR just mmx login once (the CLI keeps its own Token Plan session and Cyberine uses it; no env key needed). Tools/worker are gated on mmx being installed OR the key being set.

# install the mmx CLI per MiniMax's docs so `mmx` is on PATH, then authenticate once:
mmx                                # interactive login to your MiniMax Token Plan (or: export MMX_TOKEN_KEY=...)

# Text worker: put mmx-text-build in the writing fleet (spawns `mmx text chat --stream`)
CYBERINE_BUILD_FLEET=mmx-text-build cyberine run "summarize the architecture of this repo"

# Multimedia tools ride along in the implementer toolset whenever mmx is available — a loop
# implementer can call mmx_image_generate / mmx_speech_synthesize to write a file into its cwd:
CYBERINE_BUILD_FLEET=loop-deepseek-build cyberine run "generate a cyan hexagon logo with mmx_image_generate and save it to assets/logo.jpg"
  • CYBERINE_MMX_MODEL overrides the text model (default MiniMax-Text-01).
  • mmx_image_generate / mmx_speech_synthesize write their output RELATIVE to the worker cwd (absolute paths and .. escapes are rejected via the sandbox path resolver).
  • If mmx is installed but not logged in, the tool/worker call surfaces the auth error at run time rather than being hidden — install/login is never forced.