Audio-Visual Memory

Check the qwen-mm-plugins-omni-memory tools in your tool list for full schemas and parameters.

First decide whether this video needs a memory at all

Building one costs an omni call per 30s window, so over a short video it spends N calls indexing what fits in a single request. Decide by length, and by whether the user wants a memory.

How you learn the length: get_memory_status(video_path=...). It reports duration_min for the source video even when no memory exists, and its next_step already applies the table below — so the call you had to make anyway also answers this. (It reads the file with ffprobe; if that is unavailable the field is absent and building is the safe default.)

Length	What to do
under ~10 min	`watch_and_answer(video_path, question)` — no memory, one call, done
~10–30 min	build a memory, unless the user has said they do not want one and just wants a quick answer — then `watch_and_answer`
over ~30 min	build a memory. No exceptions. One request cannot hold that much video, so a watch will fail rather than answer badly

Two things that override the table: