GLM-4.5-Air vs Qwen3.5-2B

GLM-4.5-Air

An English and Chinese cousin for agent, coding and tool-calling work, with switchable thinking and wide runtime support. It needs about 135 GB for Z.ai's FP8 build, two to four H100s by Z.ai's figures, and Z.ai and Novita host it. The main risk is age, with files from August 2025 and no answers from Z.ai since.

Qwen3.5-2B

A small vision-language cousin for prototypes, fine-tuning and light local steps such as tool calls, tagging or reading an image, running in about 2 GB at 4 bits in every major runtime under plain Apache 2.0. Keep thinking off, since the card warns it loops. The main risk is neglect, with no safety results or answers from Alibaba since March.

GLM-4.5-Air

1. Z.ai's FP8 recipe is python3 -m sglang.launch_server --model-path zai-org/GLM-4.5-Air-FP8 --tp-size 4 --tool-call-parser glm45 --reasoning-parser glm45, and 2 H100s are enough below the full 128K context
2. Use the glm45 tool and reasoning parsers for this model, the glm47 parser in Z.ai's current README is for GLM-4.7
3. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks, which makes the template add /nothink and an empty think block
4. Declare tools in OpenAI style, and the template renders arguments as arg_key and arg_value pairs that the parser turns back into JSON
5. Keep prompts under 128,000 tokens, the tokenizer config's limit, though config.json allows 131,072
6. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented for the weights

Qwen3.5-2B

1. Smallest start is ollama run qwen3.5:2b-q4_K_M (1.9 GB); plain qwen3.5:2b pulls the 2.7 GB Q8_0 build
2. Full precision vllm serve Qwen/Qwen3.5-2B --port 8000 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder
3. Thinking is off by default; if you turn it on with "chat_template_kwargs": {"enable_thinking": true}, stream and cut off runaway output, since the card warns of thinking loops, and add --reasoning-parser qwen3 in vLLM or SGLang to split the reasoning out
4. There's no generation_config.json, so pass the card's sampling yourself, for example temperature=1.0, top_p=1.0, top_k=20, presence_penalty=2.0 for text without thinking
5. Use it for narrow steps or as a fine-tuning base, not as the main agent, as the card itself suggests
6. Validate any JSON it returns, since structured output isn't documented