MMX CLI vs qmd

MMX CLI is MiniMax's unified command-line interface for their full suite of multimodal AI models. A single tool — "mmx" — gives developers access to text generation, image generation, video generation, speech synthesis, music generation, and web search, all through a consistent command pattern. It works natively as a Claude Code or Cursor tool, enabling agents to call multimodal generation capabilities without leaving the terminal. MiniMax is the Chinese AI lab behind the Hailuo video model and MiniMax-Text-01 (a 456B parameter mixture-of-experts model). The MMX CLI essentially brings their entire model portfolio under one roof with a unified authentication and billing layer. For developers who need to mix modalities — generate an image, then narrate it with synthesized speech, then clip it into a video — this removes the need to juggle five different APIs. The Claude Code integration is the most immediately interesting angle. With MMX CLI configured as a tool, Claude can autonomously generate images and videos as part of code execution — not just describe them. This is an early taste of what "truly multimodal agentic workflows" look like in practice.

qmd is a lightweight local search engine built by Tobi Luetke, CEO of Shopify, for indexing and querying personal knowledge bases, documentation, and meeting notes — entirely offline. It combines three retrieval approaches in a single pipeline: BM25 full-text search for exact keyword matches, vector semantic search via ONNX-based embeddings, and LLM re-ranking using GGUF models through node-llama-cpp. All three stages run locally with no cloud dependency. The tool ships in multiple deployment modes: a CLI for ad-hoc queries, a Node.js library for programmatic use, an HTTP service for local API access, and — most useful for AI workflows — a native MCP server that lets Claude Code, Cursor, and similar editors query your local knowledge base directly during coding sessions. The hybrid retrieval approach means it handles both "find the exact error message from last week's standup notes" and "what was our decision about the auth architecture" equally well. What makes this notable beyond its technical approach is provenance: Luetke shipped it as a personal tool he actually uses, not a startup product. The GitHub history shows active iteration and he's been talking about it on X. It's a credible signal of where pragmatic AI-augmented knowledge management is heading for technical users who prefer local-first tools.