The LGTM (Page 3)

The LGTM

Sign in Subscribe

Claude Code 2.1.191 Fixes the Background-Agent Zombie Problem

Claude Code 2.1.191 Fixes the Background-Agent Zombie Problem

Claude Code 2.1.191 is a patch release, but the lead fix deserves a much louder headline: stopped background agents no longer resurrect. That is the kind of sentence that sounds funny until you remember that background agents are not browser tabs. They are delegated coding sessions with tools,

Codex Alpha 15 Removes the Escape Hatch From Agent Context Management

Codex Alpha 15 Removes the Escape Hatch From Agent Context Management

Codex 0.143.0-alpha.15 is the kind of release that looks dry until you ask what would break without it. Automatic compaction is no longer optional. Inter-agent messages are persisted as response items. Remote skill discovery moves to a bounded filesystem walk RPC. Executor plugin paths stay URI-native until

Qwen Code 0.19.2 Makes Permission Policy a Remote API, Not a Slash Command

Qwen Code 0.19.2 Makes Permission Policy a Remote API, Not a Slash Command

Qwen Code 0.19.2 is not really about a new command. It is about admitting that a local coding agent is no longer just a terminal process with a chat loop attached. Once the same agent can be reached through a daemon, an ACP client, a browser surface, and

Gemini 3.5 Flash Computer Use Moves Agent Safety From Blog Disclaimer to Runtime Interface

Gemini 3.5 Flash Computer Use Moves Agent Safety From Blog Disclaimer to Runtime Interface

Computer-use agents have always had a demo problem: the demo looks like magic, and the production checklist looks like an incident report waiting to happen. Google’s new Gemini 3.5 Flash computer-use capability is interesting because it moves the conversation away from “look, the model can click” and toward

OpenAI Is Positioning Codex as the Control Plane for Agentic Engineering

OpenAI’s latest Codex positioning is not really about a better coding assistant. It is about where engineering work gets routed. The refreshed Codex page describes “a coding agent that helps you build and ship with AI” and calls the app “a command center for agentic coding.” That phrase is

Codex in Chrome Is the Browser-Agent Moment Teams Need to Treat Carefully

Codex in Chrome Is the Browser-Agent Moment Teams Need to Treat Carefully

Browser agents finally got interesting when they stopped pretending the web is a clean API and started touching the ugly part: authenticated work. OpenAI’s Codex Chrome extension is not just “Codex can click buttons now.” It is Codex stepping into the same browser state developers use for QA dashboards,

Qwen Code v0.19.2 Makes Local Agent Control Planes Explicit

Qwen Code’s latest preview is not trying to win a demo reel. That is the point. v0.19.2-preview.0 is a release about turning local-agent features into daemon contracts: model-callable MCP resources, persistent workspace permission rules, faster qwen serve startup, voice dictation in the Web Shell, stricter budget

QwenPaw Adds Release-Pipeline Proof Before Desktop Agents Reach Users

QwenPaw just made a release-engineering change that deserves more attention than most model launches. PR #5428 adds end-to-end desktop UI verification to the release pipeline. Not “does the repo build?” Not “did the frontend tests pass?” The verifier installs or extracts the packaged desktop artifact, launches the same shell users

OpenClaw Finally Counts HTTP API Tokens Where Operators Spend Money

Agent cost dashboards have a simple failure mode: they look useful while quietly ignoring the path where the money is actually spent. OpenClaw PR #96227 fixes one of those failures. OpenAI-compatible HTTP ingress traffic was emitting model-call events, but not model.usage, the event that downstream consumers use for token

OpenClaw’s Inline-Eval Patch Is the Boring Guardrail Vibe Coding Needs

The boring parts of agent security keep doing the real work. OpenClaw PR #96216 is not glamorous: it teaches strict inline-eval detection that python3.13 -c, /usr/bin/pypy3.10 -c, PHP -B/-E/-R, and R/Rscript -e/--exec are still inline code execution. That sounds obvious. It was