gpt-oss-20b vs LongCat-2.5

gpt-oss-20b 90

Memory earns 25, since OpenAI's own MXFP4 build is 13.76 GB and a fifth on top is 16.5 GB, just past the 16 GB band, and Ollama's 14 GB build lands in the same 24 GB band. Runtimes earn the full 25 from model code in released Transformers, vLLM and SGLang, the architecture in llama.cpp and the model in Ollama's library. Builds earn 10, because OpenAI ships one quantised precision, MXFP4, and the original and metal folders are the same weights for its reference code. Terms earn 15 for Apache 2.0, whose usage policy only asks users to follow the law. Download earns 10, since the repository isn't gated. Hosted earns 5, with five inference providers live for it on its Hugging Face page on 1 November 2026, while OpenAI's own API lists it with no usable rate limit and isn't counted.

LongCat-2.5 35

Memory 0, the smallest build is Meituan's W4A4 repository, 1,336 GB, and 1,336 GB × 1.2 = 1,603 GB, far above 256 GB. The BF16 files are 3,562 GB. Runtimes 0, none of the six runs it in a released version: vLLM 0.33.0, SGLang 0.5.23, Transformers 5.22.2 and llama.cpp b12242 have no LongcatCausalLM or pro_v code, and the model code config.json names isn't in the repository. Builds 10, one quantised build from Meituan, the W4A4 repository (4-bit experts, 1,336 GB). Terms 15, MIT in the metadata, the LICENSE file and the card, with nothing added. Download 10, the Hub API reports gated false for both repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it. 0 + 0 + 10 + 15 + 10 + 0 = 35.

gpt-oss-20b 85

File safety earns 25, since the weights are safetensors and metal/model.bin is OpenAI's own raw Metal format rather than pickle, and nothing in the repository runs as code (a judgement call on the .bin name). Provenance earns 15, files in OpenAI's own organisation and a checksum on every file. Safety evaluation earns 10, because the published safety results for this size are OpenAI's own, and the outside review covered gpt-oss-120b. Agent guidance earns 15 for an instruction hierarchy the model was trained to follow, with prompt-injection results, though OpenAI reports it trails o4-mini there. Licence risk keeps 15, with nothing to deduct under Apache 2.0. The security programme earns 5 for OpenAI's security.txt with a Bugcrowd contact. Public advisories for the gpt-oss code couldn't be checked, so that half scores as absent.

LongCat-2.5 60

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in the meituan-longcat organisation, the name of Meituan's GitHub organisation that the card links for deployment, and the card's licence names Meituan (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions under Usage Considerations: not evaluated for every use, assess accuracy, safety and fairness before sensitive use, and follow the law. Licence risk 15, MIT with no use policy, no threshold and no right to change the terms. Security programme 0, no way to report a flaw on the card beyond a general contact, and Meituan's own security pages weren't looked up, so this scores as absent and is an open question. 25 + 15 + 0 + 5 + 15 + 0 = 60.

gpt-oss-20b 90

The chat template earns 20, a Jinja file in the repository. The tool-calling format earns 25, since OpenAI's harmony guide says how functions are declared and how calls come back, and OpenAI ships the openai-harmony parser. Trained tool calling earns 10, because each call ends the message and waits for its result, so it makes one call at a time. Structured output earns 15 for a JSON Schema given in the developer message, documented in the harmony guide. Reasoning control earns 10, with low, medium or high effort per request and the reasoning on its own channel, though it can't be switched off. Context earns 10 for 131,072 tokens, which OpenAI describes as trained in even though the config reaches it with YaRN.

LongCat-2.5 75

Chat template 20, chat_template.jinja in the repository (11,823 characters), with a copy in tokenizer_config.json. Tool-calling format 25, the card documents how tools are declared (the OpenAI function format) and how calls come back (tool_calls with an id, a name and JSON arguments, answered by a tool message), in a worked example against an OpenAI-compatible server. Trained tool calling 10, the card describes reinforcement learning on long agentic tasks and shows one tool call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output. Reasoning control 10, enable_thinking on or off per request through chat_template_kwargs, with the reasoning returned as reasoning_content, both shown on the card. Context 10, the card states no context length, but config.json gives 524,288 positions and the card's own evaluations ran at 512K and 1M sequence lengths after what it calls long-context training, so 128K or more is taken as trained. 20 + 25 + 10 + 0 + 10 + 10 = 75.