Apertus v1.5 8B vs gpt-oss-120b

Apertus v1.5 8B

A fully open 8B cousin, training data included, for multilingual chat and tool calls with images and audio in. It needs about 22 GB in BF16 and Swiss AI's own vLLM or Transformers fork, since no released runtime supports it. The main risks are a gated download with a policy to pass on and tools that fail with thinking on.

gpt-oss-120b

A reasoning and agent cousin that runs in most runtimes under Apache 2.0 with published safety work. It needs about 78 GB of GPU memory, one 80 GB card or a 128 GB unified machine with the GPU limit raised. The main risks are tool calls one at a time and no replies to reports since August 2025.

Apertus v1.5 8B

1. Accept the terms on the card and set HF_TOKEN before downloading
2. Use Swiss AI's Docker image ghcr.io/swiss-ai/vllm_apertus_1.5_release, since stock vLLM and Transformers don't load Apertus1p5ForConditionalGeneration yet
3. Serve with --chat-template-content-format string --enable-auto-tool-choice --tool-call-parser apertus for tools, and leave thinking off when you need tools
4. For thinking, set --reasoning-parser apertus and --default-chat-template-kwargs.enable_thinking true, and budget max tokens generously
5. Audio is resampled to 24 kHz and costs 40 tokens a second, and video must be passed as frames
6. Don't cast the loaded model with .half(), the image and audio tokenizers must stay in F32
7. If you redistribute the weights, the policy says you must pass it on and get the recipient's express assent

gpt-oss-120b

1. Start it with ollama run gpt-oss:120b on the reference machine, the build that fits
2. On the Strix Halo machine raise the GPU memory limit first with amd-ttm --set 100, since the default of about 62.8 GiB is below the 78 GB it needs
3. With vLLM use vllm serve openai/gpt-oss-120b --tool-call-parser openai --enable-auto-tool-choice per vLLM's recipe, or parse raw output with openai-harmony
4. Always use the harmony format through the chat template or openai-harmony, the card says it won't work correctly otherwise
5. Set Reasoning: low in the system message for short tasks, medium is the default
6. Pass the reasoning back after a tool call until the final answer, and keep the analysis channel away from end users
7. Expect one tool call per turn and loop, don't wait for parallel calls