qwen - The LGTM

The LGTM

Sign in Subscribe

qwen

A collection of 62 posts

Qwen Code’s June 5 Nightly Turns Agent Installation Into a Supply-Chain Story

Qwen Code’s June 5 Nightly Turns Agent Installation Into a Supply-Chain Story

Qwen Code’s latest nightly is not trying to win the model-benchmark news cycle. Good. The more useful story is lower in the stack: Alibaba’s open terminal agent is hardening how it gets installed, updated, copied from, and wired into GitHub automation. That sounds like release-note compost until you

Qwen3.7-Plus Makes Alibaba’s Agent Bet Multimodal — and Less Open

Qwen3.7-Plus is not Alibaba rediscovering multimodal AI. It is Alibaba drawing a much cleaner product boundary: open-weight Qwen for builders who want control, proprietary Qwen for teams that want hosted agent capacity at an aggressively low price. That split is the story. The model’s image and video inputs

Qwen Code 0.17.1 Is the Boring Agent Release Teams Should Actually Test

Qwen Code 0.17.1 Is the Boring Agent Release Teams Should Actually Test

Qwen Code 0.17.1 is not trying to win the launch-news lottery. Good. The more useful story is that Alibaba’s open terminal coding agent is accumulating the runtime scar tissue that separates a demo agent from something a team can leave inside a real repository without flinching. The

NVIDIA’s DGX Spark Update Makes Local Agents Look Less Like a Hobby and More Like Infrastructure

NVIDIA’s DGX Spark Update Makes Local Agents Look Less Like a Hobby and More Like Infrastructure

Local AI agents have spent the last two years trapped between two unsatisfying defaults: tiny models that fit on developer hardware but collapse under real repo context, and frontier APIs that work well until the bill, data policy, or network dependency becomes the product constraint. NVIDIA’s latest DGX Spark

Qwen Code’s June 2 Nightly Fixes the Boring Failures That Decide Whether Agents Survive Real Repos

Qwen Code’s June 2 Nightly Fixes the Boring Failures That Decide Whether Agents Survive Real Repos

Qwen Code’s June 2 nightly is the kind of release that will not win a benchmark slide and absolutely should show up in your coding-agent evaluation checklist. The headline is not a new model, a bigger context window, or another “agentic” demo where the repo is conveniently shaped like

Qwen Code’s June 1 Nightly Is Mostly About Not Melting Down Mid-Session

Qwen Code’s June 1 Nightly Is Mostly About Not Melting Down Mid-Session

Qwen Code’s June 1 nightly is not the kind of release that gets a keynote slide. Good. Keynote slides are usually where coding agents look best and production operators learn least. This one is a maintenance release full of pressure valves: memory monitoring, oversized-history guards, provider-specific request fixes, stricter

OpenClaw’s llama.cpp Tool-Call Bug Is What OpenAI-Compatible Really Means in Production

OpenClaw’s llama.cpp Tool-Call Bug Is What OpenAI-Compatible Really Means in Production

“OpenAI-compatible” is one of those phrases that sounds precise until production gets involved. OpenClaw PR #89070 is a good example. The endpoint shape was compatible enough for a local llama.cpp-backed model to talk through OpenClaw’s OpenAI-style completions surface. The streaming semantics were different enough to corrupt nested tool-call

OpenClaw’s Reasoning Replay Fix Is a Win for Local and Self-Hosted Coding Models

OpenClaw’s Reasoning Replay Fix Is a Win for Local and Self-Hosted Coding Models

“OpenAI-compatible” has become the USB-C port of local inference: everyone uses the shape, nobody quite agrees on the semantics, and the adapter drawer is somehow still full. OpenClaw PR #88617 is a small fix in that larger mess. It preserves replayed reasoning_content for OpenAI-compatible models when the selected model

Qwen Code’s May 30 Nightly Fixes a Rewind Bug That Exposes the Hidden State Problem in Coding Agents

Qwen Code’s May 30 Nightly Fixes a Rewind Bug That Exposes the Hidden State Problem in Coding Agents

Qwen Code’s May 30 nightly is exactly the kind of release most teams would skim past: one functional fix, a generated GitHub note, no model launch, no benchmark chart, no “agentic” fireworks. That would be a mistake. The bug it fixes is small in code and large in meaning: