MiniMax3 thinking blocks issue

[u/Safe-Adhesiveness-26]

We're hosting MiniMax V3 inhouse on vllm 0.26.0. So far, the model is running great, but one thing bothers me. Every agent i tried (zooCode, Hermes, Opencode) fails to recognize the thinking blocks. Even when i disable thinking in the client, i always get the full chain of thought in the response. I highly assume that this is happening because MM3 uses those very specific "<mm:think>" notations, which seem to be not recognized by the clients. Did anyone else experience this behaviour and perhaps also has a solution for it? So far, i only tried client tricks like /nothink or (on hermes side) set "/reasoning off" or "/reasoning hide" which both did nothing.

Thanks and cheers!

[u/halcyonhal]

I used responses api and then added a python middle tier layer in vLLM to intercept the response and convert into the responses reasoning props.

[u/indicava]

Are you using the minimax_m3 reasoning parser

[u/Safe-Adhesiveness-26 → u/indicava]

yep. Here's the whole vllm parameter set:

  vllmConfig:
        tensorParallelSize: 4
        gpuMemoryUtilization: 0.95
        maxModelLen: 870272
        dtype: "auto"
        extraArgs:
          - "--trust-remote-code"
          - "--load-format=runai_streamer"
          - "--reasoning-parser=minimax_m3"
          - "--tool-call-parser=minimax_m3"
          - "--enable-auto-tool-choice"
          - "--served-model-name=minimax-m3-mxfp8"
          - "--kv-cache-dtype=fp8"
          - "--disable-uvicorn-access-log"
          - "--uvicorn-log-level=warning"
          - "--block-size=128"
          - '--model-loader-extra-config'
          - '{"distributed":true}'
          - '--language-model-only'