Where do the pixels actually go?

"Multimodal-native" has quietly come to mean a tool call rather than a model property. Qwen's new plugin repo is honest about that; a lot of the commentary around it is not.

Qwen-MM-Plugins makes an existing agent harness handle images, video, OCR, ASR and segmentation. The README's own definition of a capability: a skill, so the model knows the toolset exists, plus an optional MCP server, the tools themselves. Apache-2.0, no tagged releases yet, about 1.6k GitHub stars in under two weeks.

None of it touches the weights. There is no adapter and no retraining, which for a harness is the right call: you add OCR to a coding agent without owning a vision stack, and the providers stay swappable.

Read the data path anyway. The local plugin reads frames and crops images on your machine. The understanding calls out to a hosted API, DashScope by default. If you are under data residency rules or genuinely air-gapped, that one line is the whole procurement conversation, and repointing it is your work, not theirs.

The trap: telling a model a tool exists is not the same as the model using it well. The failure mode moves from "cannot see the image" to "picked the wrong tool and summarised it confidently." That needs an eval per modality, and the repo ships no benchmarks.

Ask where the pixels go.