MiniCPM-o 4.5 vs occamy-1.0

MiniCPM-o 4.5

A small omni cousin that sees, listens and talks back, with full-duplex speech and voice cloning, in about 7 GB at 4-bit through llama.cpp or Ollama for text and images. Speech output needs OpenBMB's remote code or llama.cpp-omni, and 28 GB of GPU for the full demo. The main risks are repository code and pickle files and no safety results.

occamy-1.0

A Qwen3.6-35B-A3B fine-tuned for long agent work with tools, files and code, under plain Apache 2.0, and Accio's 4-bit builds run in about 23 GB. The main gaps are no safety results, agent guidance or security contact, and every benchmark figure is Accio's own.

MiniCPM-o 4.5

1. Quickest start for text and images is ollama run openbmb/minicpm-o4.5, about 6 GB
2. With vLLM 0.16.0 or later pass --trust-remote-code, and send stop_token_ids [151643, 151645] as OpenBMB's guide does
3. vLLM, llama.cpp and Ollama return text only; for speech out use the card's Transformers 4.51.0 code or OpenBMB's llama.cpp-omni
4. In llama.cpp pass both the language GGUF and MiniCPM-o-4_5-vision-F16.gguf with --mmproj, and use --jinja --reasoning-budget 0 to turn thinking off
5. Keep prompts within 40,960 tokens
6. Don't rely on tool calls or JSON output, neither is documented; validate any you get

occamy-1.0

1. Serve with --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder on vLLM 0.19.0 or SGLang 0.5.10 and later
2. BF16 is 70.2 GB, so on a 128 GB machine run it without the card's 8-way tensor parallelism
3. Keep the whole assistant message, reasoning and tool calls included, in later turns, as the card says
4. Sampling per the card is temperature 1.0, top_p 0.95, top_k 20 and presence_penalty 1.5
5. With the GGUFs, NFC-normalise input text and read TOKENIZER.md, since the files store qwen2 pre-tokenizer metadata
6. The base's MTP layer isn't in this checkpoint, Accio-Lab/occamy-1.0-MTP is an experimental separate head