InternVL3.5-GPT-OSS-20B-A4B-Preview vs Laguna M.1

InternVL3.5-GPT-OSS-20B-A4B-Preview

An image and video reader on gpt-oss-20b with an optional thinking mode, a preview untouched for over a year. It needs about 51 GB in BF16, since OpenGVLab publishes no quantised build, and runs in Transformers and vLLM. The main risk is a chat template in the Transformers-format repository that doesn't match its tokenizer, with no safety results.

Laguna M.1

A large coding and agent cousin under plain Apache 2.0, for agents with a multi-GPU server. Its smallest build needs about 167 GB, more than a 128 GB machine, and no local runtime library packages it. The main risks are no upkeep since July, no hosted fallback shown today, no safety results, and repository code on the SGLang route.

InternVL3.5-GPT-OSS-20B-A4B-Preview

1. Serve with vllm serve OpenGVLab/InternVL3_5-GPT-OSS-20B-A4B-Preview-HF --max-model-len 32768, which is our command; the card gives none for vLLM
2. Check the rendered prompt before relying on it, since the shipped template's <|im_start|> markers aren't tokens in the gpt-oss tokenizer; the GitHub-format repository's harmony template is the alternative
3. Use Transformers 4.55.0 or later, as the card requires for this size
4. For thinking, send the card's thinking system prompt and parse the reasoning out of the <think> tags, with temperature 0.6 and sampling on as the card advises
5. Keep inputs within 32K tokens, the length it was trained at, whatever the config says

Laguna M.1

1. Run the NVFP4 build on Blackwell GPUs with vllm serve poolside/Laguna-M.1-NVFP4 --tensor-parallel-size 2 --tool-call-parser poolside_v1 --reasoning-parser poolside_v1 --enable-auto-tool-choice, on vLLM 0.21.0 or later
2. Thinking is off in the template unless you pass enable_thinking true or start the server with --default-chat-template-kwargs '{"enable_thinking": true}', which Poolside recommends for agentic coding
3. Pass earlier reasoning back as reasoning_content in the history, since the card says reasoning may stop in later steps if it's dropped
4. Sampling per the card is temperature 1.0 and top_k 20
5. The FP8 build's Docker image and serve.sh predate upstream support and set a 4,096-token context, so prefer a released vLLM
6. It doesn't fit our 128 GB reference machine at any published precision
7. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented