Woodander Media
NEW IN MEDIA · GUIDE What Is Woodander? A Growth Platform for Projects That Want to Be Found
Woodander Discover Explore projects and businesses Add your project → Woodander TOP Competitive project rankings Claim a spot → Woodander Media News, stories and analysis Write a story → Woodander Market Advertising and partnerships List your channel → Woodander SEO Tools and content growth Check my website → Woodander Outreach Find relevant opportunities Build my route →
Signal AI 13 Oct, 16:57

vLLM 0.31.0 adds preload CLI and gates multimodal kwargs

vLLM 0.31.0 shipped on October 5, 2026 with a weight-cache preload CLI, draft-model speculative decoding and a breaking change for multimodal kwargs.

By Woodander Media Published Oct 13, 2026, 16:57 · 2 min read

The vLLM project released version 0.31.0 on October 5, 2026. It carries 717 commits from 307 contributors and includes a new vllm preload command, draft-model speculative decoding in Model Runner V2 and a security-motivated breaking change. If you serve models with vLLM, read the breaking changes before you upgrade.

What changed

  • The new vllm preload CLI launches a weight-cache daemon that keeps post-quantized weights in GPU memory across engine restarts.
  • Model Runner V2 gains draft-model speculative decoding and custom logits processors.
  • Per-request mm_processor_kwargs and media_io_kwargs now return an error unless the server starts with --trust-request-mm-kwargs. Server-level flags and offline LLM use are unchanged.
  • tokenizer_mode="slow" is removed, and --enable-mamba-fine-grained-prefix-cache is renamed to --enable-mamba-shared-prefix-checkpoint.
  • The release notes list a fused KimiViT QK RoPE kernel at up to 29x faster and a halved DeepGEMM FP8 workspace.

Why it matters

Restart time is a real cost when you run agents against a self-hosted model: every redeploy means reloading weights. A preload daemon attacks that directly. The multimodal change is the one to watch. Clients that pass processor kwargs per request will start failing, and we think rejecting them by default is the right call for any server exposed beyond your own team.

What to do now

  1. Search your client code for mm_processor_kwargs and media_io_kwargs. Move the values to server-level flags, or add --trust-request-mm-kwargs only if you control every caller.
  2. Grep your launch scripts for the renamed Mamba flag and the removed slow tokenizer mode.
  3. Test vllm preload on a staging box before you rely on it in production.

More from this beat is on the AI Agents & Infrastructure hub.

Sources

Woodander Media — The Woodander Media editorial team All AI news →
Latest →
Woodander Media keep growing.