forked from google/minja
-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
Feature Request
The Apertus template uses a unique format for reasoning content:
- Standard format: message.reasoning_content = "text"
- Apertus format: message.content = {"blocks": [{"type": "thoughts", "text": "..."}]}
Models Using Blocks Format
Based on research of templates in llama.cpp, there are multiple variants:
- Apertus - Uses content.blocks format with types: thoughts, tool_calls, tool_outputs, response
- Ministral 14B Reasoning - Uses message content as array of blocks (text, thinking, image, image_url)
- Mistral-Small 3.2-24B - Similar array-based blocks
- unsloth-mistral-Devstral-Small - Similar array-based blocks
OpenAI Standard
OpenAI uses a different approach - they keep content as string and add reasoning_content field:
{
"role": "assistant",
"content": "This is the actual response text",
"reasoning_content": "This is the reasoning/thinking process"
}
This is different from blocks format. Also see o1 reasoning format, DeepSeek V3, Qwen thinking, GLM-4.6
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels