GLM-5.3 vs Qwen3-Omni-30B-A3B-Instruct

GLM-5.3

A large coding and long-horizon agent model with a 1M-token context, several tool calls per turn and three reasoning budgets. Z.ai's smallest build is 756 GB in FP8, so it needs an 8-GPU server, Z.ai's API or a provider. The main risks are no published safety work, no way to report a flaw, and thinking that can't be turned off.

Qwen3-Omni-30B-A3B-Instruct

An omni-modal cousin that listens, watches and reads, then answers in text or one of three voices, with tool calls from spoken requests, under plain Apache 2.0. Its only build, BF16, needs about 85 GB, and speech out needs Transformers or vLLM-Omni. The main risk is no answers from Qwen and no safety work for speech-driven actions.

GLM-5.3

1. Start it with vllm serve zai-org/GLM-5.3 --kv-cache-dtype fp8 --tensor-parallel-size 8 --speculative-config.method mtp --speculative-config.num_speculative_tokens 5 --tool-call-parser glm47 --reasoning-parser glm47 --enable-auto-tool-choice --served-model-name glm-5.3 (vLLM 0.28.0 or later, 8xH200 or 8xH20 per vLLM's recipe)
2. Use the glm47 tool-call and reasoning parsers in vLLM or SGLang; SGLang's cookbook says glm45 leaves the calls as plain text
3. Pass chat_template_kwargs: {"reasoning_effort": "low"} for short tasks; anything other than low or high falls back to max
4. Pass clear_thinking: true in chat use, since the template keeps earlier reasoning by default
5. Don't send enable_thinking: false; the template ignores it and always opens a think block
6. Validate JSON output yourself, since structured output is documented only for Z.ai's hosted API
7. No Z.ai build fits a 128 GB machine; the full 1M context needs 8xB200 per vLLM's recipe

Qwen3-Omni-30B-A3B-Instruct

1. For text answers, mkdir -p media && vllm serve Qwen/Qwen3-Omni-30B-A3B-Instruct --dtype bfloat16 --max-model-len 32768 --allowed-local-media-path "$(pwd)/media" with vLLM 0.11.1 or later serves the Thinker on an OpenAI-compatible API
2. The card's command passes --allowed-local-media-path /, which lets anyone who can reach the server have it read any file on the machine through a file:// URL. Point it at a dedicated folder that holds only the media you mean to send, as above, and give vLLM an absolute path
3. Send audio as audio_url and images as image_url content parts; vLLM serve doesn't take use_audio_in_video, so pass a video's audio separately
4. For speech out, load Qwen3OmniMoeForConditionalGeneration in Transformers 4.57.0 or later with qwen-omni-utils, pick speaker Ethan, Chelsie or Aiden, and write the returned waveform at 24 kHz
5. Call model.disable_talker() or pass return_audio=False when you only need text, which saves about 10 GB and time
6. Parse tool calls as JSON inside <tool_call> tags yourself, since no parser is named, and confirm actions triggered by speech before running them
7. Keep use_audio_in_video the same across every step of a conversation, the card warns results go wrong otherwise
8. Budget memory for video, the card's table rises from 78.85 GB for 15 seconds to 144.81 GB for 120 seconds in BF16