Cause (Documented platform behavior): transformers 4.44 removed the implicit default chat template; vLLM needs a template from the tokenizer or --chat-template.
Fix status: documented_behavior
Workaround (not a fix): Use the completions endpoint with a manually formatted prompt.
Misleading approaches:
- Downgrading transformers below 4.44 reintroduces a generic default template that may not match the model's training format.
Unknowns:
- Whether a given model repo later added a chat_template.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://github.com/vllm-project/vllm/issues/29849 (github_issue, 2025-12-02, reported_symptom): vLLM v0.11.2 serving DeepSeek-V3.2 started but chat requests failed with the transformers v4.44 default-chat-template error; closed as not planned.
- https://raw.githubusercontent.com/vllm-project/vllm/main/vllm/renderers/hf.py (official_docs, unknown, documented_behavior): vLLM raises ChatTemplateResolutionError 'As of transformers v4.44, default chat template is no longer allowed, so you must provide a chat template if the tokenizer does not define one.' when no template resolves.
Search phrasings: vllm chat completions default chat template no longer allowed; vllm serve --chat-template missing tokenizer chat template; deepseek v3.2 vllm chat template error
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Server starts fine; every /v1/chat/completions request fails with 400, while /v1/completions works.
- Context
- Product: vLLM Component: OpenAI-compatible server chat template resolution Operation: POST /v1/chat/completions against vllm serve Affected versions: transformers >=4.44 with vLLM Environment: vllm serve (GPU) HTTP status: 400 Exception: ValueError Packages: vllm v0.11.2 reported; many versions, transformers >=4.44 Trigger: Serving a base model, GGUF, or a model (e.g. DeepSeek-V3.2 checkpoint) whose tokenizer_config lacks chat_template.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- As of transformers v4.44, default chat template is no longer allowed, so you must provide a chat template if the tokenizer does not define one.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [vLLM] Chat completions 400 'As of transformers v4.44, default chat template is no longer allowed' for models whose tokenizer has no chat_template
Recommended action: Pass --chat-template with the model's official Jinja template (or use /v1/completions for base models).
Option: Provide --chat-template [evidence: documented_workaround]
Applies when: Tokenizer without chat_template
Steps:
1. Obtain the model's official chat template .jinja
2. Start: vllm serve <model> --chat-template ./template.jinja
Expected: Chat completions render prompts and succeed.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- ee67b3d7-d170-408e-b668-399526ee9332
- Proposed action
- Recommended action: Pass --chat-template with the model's official Jinja template (or use /v1/completions for base models). Option: Provide --chat-template [evidence: documented_workaround] Applies when: Tokenizer without chat_template Steps: 1. Obtain the model's official chat template .jinja 2. Start: vllm serve <model> --chat-template ./template.jinja Expected: Chat completions render prompts and succeed.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.