Devotd Github
ReleaseInference & serving

cutlerbenjamin1-cmd/qwen38-megakernel v2026.10.31.1 — input and GPU error fixes

cutlerbenjamin1-cmd/qwen38-megakernel v2026.10.31.1 is the second stabilization release of a standalone OpenAI-compatible server that adjusts video input handling and property responses, and fixes result differences that occurred on some GPUs.

Repositorycutlerbenjamin1-cmd/qwen38-megakernel ↗

cutlerbenjamin1-cmd/qwen38-megakernel v2026.10.31.1 is the second stabilization release of a standalone OpenAI-compatible server that adjusts video input handling and property responses, and fixes result differences that occurred on some GPUs.

GitHub description: Standalone OpenAI-compatible server for Qwen3.8-27B on one 24 GB NVIDIA GPU: CUDA megakernel (from open-jet), CPU vision encoder, launcher

stars
★ 5
Forks
1
Language
Cuda
License
AGPL-3.0
Latest release
v2026.10.31.1
Read original source ↗View on GitHub ↗

cutlerbenjamin1-cmd/qwen38-megakernel v2026.10.31.1 is the release of a standalone OpenAI-compatible server that serves Qwen3.8-27B on a single 24 GB NVIDIA GPU. According to the release summary, it is the second stabilization version of the same engine. This time, video input has been restricted to actual media containers. Property responses now show only whether a key is configured, not the API key value. It also fixes a bug where results differed on some GPUs. The changes are published in the GitHub release log.

The focus of this repository is a server configuration that runs Qwen3.8-27B on a single 24 GB NVIDIA GPU. The components described are a CUDA megakernel taken from open-jet, a CPU vision encoder, and a launcher for running it. The changes in this version are not a new model or a performance improvement announcement, but stabilization work that adjusts the input scope and property responses and corrects GPU-related bugs. So the key point, rather than feature expansion, is making the behavior of inputs and responses clear and fixing the result differences on some GPUs.

However, the release summary does not specifically state which media containers are allowed, nor which GPUs were producing the differing results. The information provided also contains no measurements showing performance or result differences before and after the fix. It is therefore difficult to judge the supported range or the extent of the performance improvement from this release alone, and the confirmed changes are limited to the three stated fixes.